Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b6a95f49c85b88298cc7f467a2236521e5539a41b49a1fc041388549666de3b

Tx prefix hash: d50090db5b84b55e23c941b74be3aec9bb87be0c84bb16ccedb6f4ed058a8e1b
Tx public key: d1ada24a1d65bec58d675792ef63a3e3eef6471e4c07512a7ea44f2a781ced2a
Timestamp: 1751347335 Timestamp [UCT]: 2025-07-01 05:22:15 Age [y:d:h:m:s]: 00:143:12:27:27
Block: 1316340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100764 RingCT/type: yes/0
Extra: 01d1ada24a1d65bec58d675792ef63a3e3eef6471e4c07512a7ea44f2a781ced2a021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8e59396830bbe52df45e6f110510f0e35d364fc6a33aef75d97921f53783cfe 0.600000000000 1803999 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": 1316350, "vin": [ { "gen": { "height": 1316340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8e59396830bbe52df45e6f110510f0e35d364fc6a33aef75d97921f53783cfe" } } ], "extra": [ 1, 209, 173, 162, 74, 29, 101, 190, 197, 141, 103, 87, 146, 239, 99, 163, 227, 238, 246, 71, 30, 76, 7, 81, 42, 126, 164, 79, 42, 120, 28, 237, 42, 2, 17, 0, 0, 0, 3, 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