Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3afcf4f602ee2ad21f2533fb2e064aba75524a68e0cb4bf40f752a1561cb4c52

Tx prefix hash: 77b06ba3adda7c63a5184a8782761a972ab773543bb2ae7c89d60558e7ee7011
Tx public key: 5bf2fb1acd56f7c24f2d846be801696edd9ba7a3bce6553f33f5236be9705ee2
Timestamp: 1737117269 Timestamp [UCT]: 2025-01-17 12:34:29 Age [y:d:h:m:s]: 00:078:12:46:27
Block: 1199314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55901 RingCT/type: yes/0
Extra: 015bf2fb1acd56f7c24f2d846be801696edd9ba7a3bce6553f33f5236be9705ee2021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d74564e2432baec9b10a4ba6b782f31c185502d7222eb89324c3c225aca61fe8 0.600000000000 1685945 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": 1199324, "vin": [ { "gen": { "height": 1199314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d74564e2432baec9b10a4ba6b782f31c185502d7222eb89324c3c225aca61fe8" } } ], "extra": [ 1, 91, 242, 251, 26, 205, 86, 247, 194, 79, 45, 132, 107, 232, 1, 105, 110, 221, 155, 167, 163, 188, 230, 85, 63, 51, 245, 35, 107, 233, 112, 94, 226, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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