Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbfbca29e9f7094ef1de5be63c4af65e0a39877344e7d34a8aac8dbae50757a3

Tx prefix hash: 0c3a94a123b762449584410e706360302d3b719571faa5bb13d3a695f474f2bc
Tx public key: f8517caa2304b9fb5d7e0e28e72a1deefb20970344c080d9656ca1f9f89e1405
Timestamp: 1760560300 Timestamp [UCT]: 2025-10-15 20:31:40 Age [y:d:h:m:s]: 00:076:08:41:14
Block: 1390704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54673 RingCT/type: yes/0
Extra: 01f8517caa2304b9fb5d7e0e28e72a1deefb20970344c080d9656ca1f9f89e14050211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42414e103f837c76a7fd42aa72ec8634d51c59fb844fe160c4519c8f9946dceb 0.600000000000 1878951 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": 1390714, "vin": [ { "gen": { "height": 1390704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42414e103f837c76a7fd42aa72ec8634d51c59fb844fe160c4519c8f9946dceb" } } ], "extra": [ 1, 248, 81, 124, 170, 35, 4, 185, 251, 93, 126, 14, 40, 231, 42, 29, 238, 251, 32, 151, 3, 68, 192, 128, 217, 101, 108, 161, 249, 248, 158, 20, 5, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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