Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: dce018e1ce778a83f7e7d6777e389cc5f5d13a84282bdb30894d9fc81374ded1

Tx prefix hash: bb24d54f0fbc42414c3ef02d5641730cdca6be16f5294538324b633d6cb150cb
Tx public key: b51d5e426065f33fbdd3d7c3eca7d4ef443912a155c04094c3588484d33d0606
Timestamp: 1711658831 Timestamp [UCT]: 2024-03-28 20:47:11 Age [y:d:h:m:s]: 01:047:09:39:46
Block: 988420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294859 RingCT/type: yes/0
Extra: 01b51d5e426065f33fbdd3d7c3eca7d4ef443912a155c04094c3588484d33d060602110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63092ed4cc33d5fdb9e7c13409c54ff62af013147e3a8b953d321b5f77eafb14 0.600000000000 1448699 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 988430, "vin": [ { "gen": { "height": 988420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63092ed4cc33d5fdb9e7c13409c54ff62af013147e3a8b953d321b5f77eafb14" } } ], "extra": [ 1, 181, 29, 94, 66, 96, 101, 243, 63, 189, 211, 215, 195, 236, 167, 212, 239, 68, 57, 18, 161, 85, 192, 64, 148, 195, 88, 132, 132, 211, 61, 6, 6, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8