Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4232949d7156c3117b73061e25b6cd5698773ad7d327bba292ef0daaa38c371

Tx prefix hash: c6a3012e17ae70d768291df137a97c78a7d653be8d7c691bfa35de5eee010542
Tx public key: 701b5e4a3d7afd948bb32a09a7352903148cc2d52ebcf6408ba504efcb1d96a9
Timestamp: 1724028824 Timestamp [UCT]: 2024-08-19 00:53:44 Age [y:d:h:m:s]: 00:225:00:44:52
Block: 1090961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160689 RingCT/type: yes/0
Extra: 01701b5e4a3d7afd948bb32a09a7352903148cc2d52ebcf6408ba504efcb1d96a902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44d4ad2fc4a53a75aa25990752dd5f8ef241e4779dc679dfca161c90609d430c 0.600000000000 1565586 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": 1090971, "vin": [ { "gen": { "height": 1090961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44d4ad2fc4a53a75aa25990752dd5f8ef241e4779dc679dfca161c90609d430c" } } ], "extra": [ 1, 112, 27, 94, 74, 61, 122, 253, 148, 139, 179, 42, 9, 167, 53, 41, 3, 20, 140, 194, 213, 46, 188, 246, 64, 139, 165, 4, 239, 203, 29, 150, 169, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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