Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 899fe4f78e4a59269daf8cb3de553b812a67afebf55e2a94d77a01db70f56a5d

Tx prefix hash: 9e2a38982bbb9b3fb3a56afe8e9853e68250ac55975eb70464ec65f6eebe26d1
Tx public key: ffc8dcddf3c9294c661960e8291d41690ca0b3b5f3b9f434283e4badfd16f7ad
Timestamp: 1757461116 Timestamp [UCT]: 2025-09-09 23:38:36 Age [y:d:h:m:s]: 00:112:06:05:27
Block: 1365052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80339 RingCT/type: yes/0
Extra: 01ffc8dcddf3c9294c661960e8291d41690ca0b3b5f3b9f434283e4badfd16f7ad021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1f140c73655eb2f50e16c1ed4411501d3004ea30a23c8da754edbcfe5dd56e3 0.600000000000 1853091 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": 1365062, "vin": [ { "gen": { "height": 1365052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1f140c73655eb2f50e16c1ed4411501d3004ea30a23c8da754edbcfe5dd56e3" } } ], "extra": [ 1, 255, 200, 220, 221, 243, 201, 41, 76, 102, 25, 96, 232, 41, 29, 65, 105, 12, 160, 179, 181, 243, 185, 244, 52, 40, 62, 75, 173, 253, 22, 247, 173, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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