Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 978f339e30e791f296e8905abc0ad97c79005e12855654001bb4804bc0925fd8

Tx prefix hash: 2e31d85cddc085585f45f98ffc842e37518679cd0e9039d2468950a42db447d3
Tx public key: 0ab7a3abcedc21f319ef6d33fbc1b810de0eb6a8e55b49580e2d1054b9b71a21
Timestamp: 1704494920 Timestamp [UCT]: 2024-01-05 22:48:40 Age [y:d:h:m:s]: 01:103:10:46:35
Block: 928998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335060 RingCT/type: yes/0
Extra: 010ab7a3abcedc21f319ef6d33fbc1b810de0eb6a8e55b49580e2d1054b9b71a210211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82a3e98f4f542e0c1c332e6c5dd740a3fb33e335b2657e0bcbd1904d3a80581b 0.600000000000 1386866 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": 929008, "vin": [ { "gen": { "height": 928998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82a3e98f4f542e0c1c332e6c5dd740a3fb33e335b2657e0bcbd1904d3a80581b" } } ], "extra": [ 1, 10, 183, 163, 171, 206, 220, 33, 243, 25, 239, 109, 51, 251, 193, 184, 16, 222, 14, 182, 168, 229, 91, 73, 88, 14, 45, 16, 84, 185, 183, 26, 33, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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