Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e009b1c66d9243f8fafe2de6441520d82ec0951eb9efbc05f8a423eb70a217e2

Tx prefix hash: c28e9345e56f2758efd9be31f9869a8dc25ef4d057ac432ba1d75e07644f8d56
Tx public key: 3ad787aec70ce8251e9a163dafd2953e217e8c26cfcf287a04dc6ed4a8d3da95
Timestamp: 1746166774 Timestamp [UCT]: 2025-05-02 06:19:34 Age [y:d:h:m:s]: 00:203:18:08:33
Block: 1273966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143341 RingCT/type: yes/0
Extra: 013ad787aec70ce8251e9a163dafd2953e217e8c26cfcf287a04dc6ed4a8d3da950211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8325d04456eb3cd63388ac9cb39f48b3e3f9d47bdee69815899395b0439ffbca 0.600000000000 1761253 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": 1273976, "vin": [ { "gen": { "height": 1273966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8325d04456eb3cd63388ac9cb39f48b3e3f9d47bdee69815899395b0439ffbca" } } ], "extra": [ 1, 58, 215, 135, 174, 199, 12, 232, 37, 30, 154, 22, 61, 175, 210, 149, 62, 33, 126, 140, 38, 207, 207, 40, 122, 4, 220, 110, 212, 168, 211, 218, 149, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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