Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d594d7797ad06a9ca62ff2a2800db15239457c33be0030bfc81ea81d055f07f

Tx prefix hash: af0e1349d9a72d8c1b07fb69eee4481a7dd7aa4246af99254f30729544abb00c
Tx public key: 210ec2e1b5c52e32599d37fb163dfcf775f0955f5fecb60f8ec03cdaa3f28f39
Timestamp: 1737626563 Timestamp [UCT]: 2025-01-23 10:02:43 Age [y:d:h:m:s]: 00:145:06:39:39
Block: 1203490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103582 RingCT/type: yes/0
Extra: 01210ec2e1b5c52e32599d37fb163dfcf775f0955f5fecb60f8ec03cdaa3f28f390211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2ed5212d3bee51d22fa6dd3d287427f1ed3e78bb52e408f3256ae8de62084b8 0.600000000000 1690167 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": 1203500, "vin": [ { "gen": { "height": 1203490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2ed5212d3bee51d22fa6dd3d287427f1ed3e78bb52e408f3256ae8de62084b8" } } ], "extra": [ 1, 33, 14, 194, 225, 181, 197, 46, 50, 89, 157, 55, 251, 22, 61, 252, 247, 117, 240, 149, 95, 95, 236, 182, 15, 142, 192, 60, 218, 163, 242, 143, 57, 2, 17, 0, 0, 0, 1, 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