Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62765d96eb3dbdeaa08a83ec0429a5b94b15f48c957fa58c919d543cfddf6cff

Tx prefix hash: 970d8ed963762fbc9281a1436c76c6fd6fecc0562c1443c63c4244256cf6c714
Tx public key: ffe0ba0a2d84968a7ed60bbf34a4f10b2c93b42e35c16349b2ee3c29eea401f7
Timestamp: 1729094627 Timestamp [UCT]: 2024-10-16 16:03:47 Age [y:d:h:m:s]: 00:171:07:08:27
Block: 1132965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122192 RingCT/type: yes/0
Extra: 01ffe0ba0a2d84968a7ed60bbf34a4f10b2c93b42e35c16349b2ee3c29eea401f702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e783f9b89923448f7467883d7be2b77ff811056af763de587c7efc7914e366b 0.600000000000 1616016 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": 1132975, "vin": [ { "gen": { "height": 1132965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e783f9b89923448f7467883d7be2b77ff811056af763de587c7efc7914e366b" } } ], "extra": [ 1, 255, 224, 186, 10, 45, 132, 150, 138, 126, 214, 11, 191, 52, 164, 241, 11, 44, 147, 180, 46, 53, 193, 99, 73, 178, 238, 60, 41, 238, 164, 1, 247, 2, 17, 0, 0, 0, 3, 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