Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f091e512280a3c41c6aa1d30ded382fe2d89663c5f2e36eddcf523b7a22d65ef

Tx prefix hash: 34d63b180ea601447a7741c5332a8f67f4d0f942cdf0eb671d8f189cf0845ef4
Tx public key: e1302d77f3295325e82bebb77a85a7955a8c6b85827371568ab803b773e8167c
Timestamp: 1755352033 Timestamp [UCT]: 2025-08-16 13:47:13 Age [y:d:h:m:s]: 00:139:18:32:14
Block: 1347862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99763 RingCT/type: yes/0
Extra: 01e1302d77f3295325e82bebb77a85a7955a8c6b85827371568ab803b773e8167c02110000000cd8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b29524319cf20b061d90b4c8f32c2caafade54430161f080b36554df63045bd4 0.600000000000 1835783 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": 1347872, "vin": [ { "gen": { "height": 1347862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b29524319cf20b061d90b4c8f32c2caafade54430161f080b36554df63045bd4" } } ], "extra": [ 1, 225, 48, 45, 119, 243, 41, 83, 37, 232, 43, 235, 183, 122, 133, 167, 149, 90, 140, 107, 133, 130, 115, 113, 86, 138, 184, 3, 183, 115, 232, 22, 124, 2, 17, 0, 0, 0, 12, 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