Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768392518194f21a626d005dc2b4df0db7ab6be761aa448e6ce46102121a5291

Tx prefix hash: 4c5582782716a2209fc5724b9a087e51cfdf79a44066d330b1be568917ff5d1e
Tx public key: 50ee8470b15b8be89d68029b8b3631eb480e6bc8d3c2f1dca275b8249b2d806a
Timestamp: 1751059574 Timestamp [UCT]: 2025-06-27 21:26:14 Age [y:d:h:m:s]: 00:141:05:01:56
Block: 1314084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98995 RingCT/type: yes/0
Extra: 0150ee8470b15b8be89d68029b8b3631eb480e6bc8d3c2f1dca275b8249b2d806a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac4182f9e14f89cd0b13b98127769939ef6771c3738b1fa9c2e61e1eb171f17a 0.600000000000 1801729 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": 1314094, "vin": [ { "gen": { "height": 1314084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac4182f9e14f89cd0b13b98127769939ef6771c3738b1fa9c2e61e1eb171f17a" } } ], "extra": [ 1, 80, 238, 132, 112, 177, 91, 139, 232, 157, 104, 2, 155, 139, 54, 49, 235, 72, 14, 107, 200, 211, 194, 241, 220, 162, 117, 184, 36, 155, 45, 128, 106, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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