Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78b29139f95504112362dbf2417d65c44231d9a9e156460bc0a40d1df2156851

Tx prefix hash: 2d2568bcaed149ba1c7ba3d8fdc37ae4e26070175f30260825779fe4d239c6e2
Tx public key: 8a329165731ba1ca06e57d9659ee7e05e65d07f58e516ac741b3244555b9e44a
Timestamp: 1711711851 Timestamp [UCT]: 2024-03-29 11:30:51 Age [y:d:h:m:s]: 01:218:21:37:27
Block: 988864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415096 RingCT/type: yes/0
Extra: 018a329165731ba1ca06e57d9659ee7e05e65d07f58e516ac741b3244555b9e44a0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13f047cdb22e0bb089c8ce6d0b19ba373c13a5c5f57780cfef876cc4d0e8b208 0.600000000000 1449151 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": 988874, "vin": [ { "gen": { "height": 988864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13f047cdb22e0bb089c8ce6d0b19ba373c13a5c5f57780cfef876cc4d0e8b208" } } ], "extra": [ 1, 138, 50, 145, 101, 115, 27, 161, 202, 6, 229, 125, 150, 89, 238, 126, 5, 230, 93, 7, 245, 142, 81, 106, 199, 65, 179, 36, 69, 85, 185, 228, 74, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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