Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e634001f5892b516afb8149b202c12183702e96cbf07e578a23b81d94b4d6b9a

Tx prefix hash: b770f30091058ceee48d40d38115bd6b0c35468c26c090a0f8438853896eb3c9
Tx public key: 1a1eac53dc2efdabaa3f1642cfc10cd8aa5cc2d7fb9b777731e49cd1aa723b41
Timestamp: 1716299470 Timestamp [UCT]: 2024-05-21 13:51:10 Age [y:d:h:m:s]: 00:322:16:10:14
Block: 1026887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230614 RingCT/type: yes/0
Extra: 011a1eac53dc2efdabaa3f1642cfc10cd8aa5cc2d7fb9b777731e49cd1aa723b410211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caf284abad578e75e35017c276f8011150236b62c163164aa163c70bf358d74c 0.600000000000 1494214 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": 1026897, "vin": [ { "gen": { "height": 1026887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caf284abad578e75e35017c276f8011150236b62c163164aa163c70bf358d74c" } } ], "extra": [ 1, 26, 30, 172, 83, 220, 46, 253, 171, 170, 63, 22, 66, 207, 193, 12, 216, 170, 92, 194, 215, 251, 155, 119, 119, 49, 228, 156, 209, 170, 114, 59, 65, 2, 17, 0, 0, 0, 1, 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