Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9efec6fac372917c0080012cbcd21172ab510050d98c481b4b145e09e3cf94f5

Tx prefix hash: 3f58a482d8497cca9162225550543837383f918d3916ca3fb99708f62ba0efc7
Tx public key: 8c5086c8d44e8ff6fb5476ce6ccd757e8d4d78aa0788c0ce016c0e5814fc2a3a
Timestamp: 1732238373 Timestamp [UCT]: 2024-11-22 01:19:33 Age [y:d:h:m:s]: 00:002:00:29:27
Block: 1158928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1449 RingCT/type: yes/0
Extra: 018c5086c8d44e8ff6fb5476ce6ccd757e8d4d78aa0788c0ce016c0e5814fc2a3a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a45da5b26537224b68e0ae9040a3fd9b67fdd33a294ca4cb95fd79f5856bc724 0.600000000000 1644559 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": 1158938, "vin": [ { "gen": { "height": 1158928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a45da5b26537224b68e0ae9040a3fd9b67fdd33a294ca4cb95fd79f5856bc724" } } ], "extra": [ 1, 140, 80, 134, 200, 212, 78, 143, 246, 251, 84, 118, 206, 108, 205, 117, 126, 141, 77, 120, 170, 7, 136, 192, 206, 1, 108, 14, 88, 20, 252, 42, 58, 2, 17, 0, 0, 0, 3, 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