Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f91e5521710282b35f82249ba97c410f20fce0a0322a4e784eeacc2a92100f0f

Tx prefix hash: e540ac2bfd147f3a3b61bc992f0134c28e5faa550e794086f3a3d9a23784a984
Tx public key: d3f0195e02215cfc00be26ab75994b6e17f82670ee14ab3d280a91a3c05b5caf
Timestamp: 1749620588 Timestamp [UCT]: 2025-06-11 05:43:08 Age [y:d:h:m:s]: 00:152:14:02:34
Block: 1302553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106745 RingCT/type: yes/0
Extra: 01d3f0195e02215cfc00be26ab75994b6e17f82670ee14ab3d280a91a3c05b5caf021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4a066f1d310363985cd1e86f9fefd74d41a83c71d4e3a81718910682012442e 0.600000000000 1790124 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": 1302563, "vin": [ { "gen": { "height": 1302553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4a066f1d310363985cd1e86f9fefd74d41a83c71d4e3a81718910682012442e" } } ], "extra": [ 1, 211, 240, 25, 94, 2, 33, 92, 252, 0, 190, 38, 171, 117, 153, 75, 110, 23, 248, 38, 112, 238, 20, 171, 61, 40, 10, 145, 163, 192, 91, 92, 175, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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