Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b48c53ffb108cd7b200823bb8d40e420b9bcfd72d23c182fe35f57f30251f258

Tx prefix hash: 7cec3cdd69bac6cbf0c232317f3c5e6d6ca58eeb6761e7ea768d2921d7eeadac
Tx public key: 0bd63019b5afe2141ae49e51cb14ecfdc44b9367fda54843d5d026c2273f648b
Timestamp: 1759587417 Timestamp [UCT]: 2025-10-04 14:16:57 Age [y:d:h:m:s]: 00:090:21:20:46
Block: 1382640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65087 RingCT/type: yes/0
Extra: 010bd63019b5afe2141ae49e51cb14ecfdc44b9367fda54843d5d026c2273f648b02110000000297baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b40a5c51cf4205bb64d2cecb0e906413ab7ab0186822fdbcb93fc242fc65877 0.600000000000 1870775 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": 1382650, "vin": [ { "gen": { "height": 1382640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b40a5c51cf4205bb64d2cecb0e906413ab7ab0186822fdbcb93fc242fc65877" } } ], "extra": [ 1, 11, 214, 48, 25, 181, 175, 226, 20, 26, 228, 158, 81, 203, 20, 236, 253, 196, 75, 147, 103, 253, 165, 72, 67, 213, 208, 38, 194, 39, 63, 100, 139, 2, 17, 0, 0, 0, 2, 151, 186, 249, 34, 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