Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e065d1002e3b081f96469f82b8902c5490c6d4f00b6c7b2f4bc77dfdc8deca3

Tx prefix hash: fcc64cb1e0556228115bf3c778050ea2933fe0b1562de3ae3dcb78b12d5ef5fe
Tx public key: 21a784ca61903750e9b4cf1a5d3ea7b3f67d3f9214ec40276acf3f0dce19ce39
Timestamp: 1728423762 Timestamp [UCT]: 2024-10-08 21:42:42 Age [y:d:h:m:s]: 00:173:05:53:07
Block: 1127381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123613 RingCT/type: yes/0
Extra: 0121a784ca61903750e9b4cf1a5d3ea7b3f67d3f9214ec40276acf3f0dce19ce3902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df91587d1fb445229f2ac6ad531e7ecc355629c8ebf5cb85e2bbebea08395d11 0.600000000000 1610186 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": 1127391, "vin": [ { "gen": { "height": 1127381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df91587d1fb445229f2ac6ad531e7ecc355629c8ebf5cb85e2bbebea08395d11" } } ], "extra": [ 1, 33, 167, 132, 202, 97, 144, 55, 80, 233, 180, 207, 26, 93, 62, 167, 179, 246, 125, 63, 146, 20, 236, 64, 39, 106, 207, 63, 13, 206, 25, 206, 57, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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