Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1eedddfa795f36f94f9c00717926d1e563990cfb4d6381661dc68d58cf3f3b3

Tx prefix hash: b1bd36462752b2e14966075b76ee068eef1ce43beda361c311d594357a883ae8
Tx public key: 1b10acfd6a84c3df98170dd221198d87f1b7b8d38dc404baafb3f18bc5485e72
Timestamp: 1750864450 Timestamp [UCT]: 2025-06-25 15:14:10 Age [y:d:h:m:s]: 00:195:08:22:33
Block: 1312598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137627 RingCT/type: yes/0
Extra: 011b10acfd6a84c3df98170dd221198d87f1b7b8d38dc404baafb3f18bc5485e72021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ea16c45bcae73a090140a2587bfe2451c7c06fe02887c0422263b3c60376f60 0.600000000000 1800231 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": 1312608, "vin": [ { "gen": { "height": 1312598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ea16c45bcae73a090140a2587bfe2451c7c06fe02887c0422263b3c60376f60" } } ], "extra": [ 1, 27, 16, 172, 253, 106, 132, 195, 223, 152, 23, 13, 210, 33, 25, 141, 135, 241, 183, 184, 211, 141, 196, 4, 186, 175, 179, 241, 139, 197, 72, 94, 114, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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