Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0bbbca08a06bf2933c81dd2546dff280f04fffc77e219c9223fdcbf14afe973

Tx prefix hash: 2ec0e6ed8a1817473c4db57a5d7d793a118655e6ddec036deb31f9c7cb45b0ce
Tx public key: 2cc2ffc0f8d837c4698061b79d3a4177ca7126d1008f9a5002b54828c202b57a
Timestamp: 1707439448 Timestamp [UCT]: 2024-02-09 00:44:08 Age [y:d:h:m:s]: 01:128:12:10:28
Block: 953409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352842 RingCT/type: yes/0
Extra: 012cc2ffc0f8d837c4698061b79d3a4177ca7126d1008f9a5002b54828c202b57a02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57ea0b4a9acf7080deeb9f829921971ca15304c2c8f8a9cc3e540e2382a6876a 0.600000000000 1412611 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": 953419, "vin": [ { "gen": { "height": 953409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57ea0b4a9acf7080deeb9f829921971ca15304c2c8f8a9cc3e540e2382a6876a" } } ], "extra": [ 1, 44, 194, 255, 192, 248, 216, 55, 196, 105, 128, 97, 183, 157, 58, 65, 119, 202, 113, 38, 209, 0, 143, 154, 80, 2, 181, 72, 40, 194, 2, 181, 122, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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