Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c247bac8236212072754ebb4616e730367e7bc992f71e4f516bbe614a1c4dc9

Tx prefix hash: 43422b82f39576a71c19a82b6e1af23ba3fc2071ca6e6a2ab0630000e56501e2
Tx public key: 4033e1aaea2b6338390f140f9c3f1f94867b4f14fe7ecb27a52142337e42043f
Timestamp: 1719403016 Timestamp [UCT]: 2024-06-26 11:56:56 Age [y:d:h:m:s]: 00:296:02:45:42
Block: 1052596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211612 RingCT/type: yes/0
Extra: 014033e1aaea2b6338390f140f9c3f1f94867b4f14fe7ecb27a52142337e42043f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee5849aac8697aec6f69812a851fd593092ae33e171b46c0ef1e1cf5c64da5b9 0.600000000000 1522927 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": 1052606, "vin": [ { "gen": { "height": 1052596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee5849aac8697aec6f69812a851fd593092ae33e171b46c0ef1e1cf5c64da5b9" } } ], "extra": [ 1, 64, 51, 225, 170, 234, 43, 99, 56, 57, 15, 20, 15, 156, 63, 31, 148, 134, 123, 79, 20, 254, 126, 203, 39, 165, 33, 66, 51, 126, 66, 4, 63, 2, 17, 0, 0, 0, 2, 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