Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b711d667c63e01e8d972d5bd883fb3d24c6528f1166583ffb90465abf4bf384

Tx prefix hash: 0163173c0989179b3253f9d13825ac81d3b530df7e3235e7decd5bcf5574f7ad
Tx public key: e2cbd3fd1e07216030885763bc375768a27a95c1dc92d7051a0e0d9da3198689
Timestamp: 1734615249 Timestamp [UCT]: 2024-12-19 13:34:09 Age [y:d:h:m:s]: 00:095:19:57:15
Block: 1178637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68244 RingCT/type: yes/0
Extra: 01e2cbd3fd1e07216030885763bc375768a27a95c1dc92d7051a0e0d9da31986890211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bf2759884699e30d838778418ef52f0ddd630416ffcc11b6526f2c1d51d66f9 0.600000000000 1665026 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": 1178647, "vin": [ { "gen": { "height": 1178637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bf2759884699e30d838778418ef52f0ddd630416ffcc11b6526f2c1d51d66f9" } } ], "extra": [ 1, 226, 203, 211, 253, 30, 7, 33, 96, 48, 136, 87, 99, 188, 55, 87, 104, 162, 122, 149, 193, 220, 146, 215, 5, 26, 14, 13, 157, 163, 25, 134, 137, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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