Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ed1d5643c952e1c3da7718bf1a7bfcb0ca5cc9b424a21110bbc62f8e6d88074

Tx prefix hash: 0bc5d627b3fabf47fdbd24224feb8156d17c8ad46b11b6735b76161fa337fefb
Tx public key: 121e716b649c31616a34ec339a13bfcd359a3c43a85bb809e83c0852b75d7bbc
Timestamp: 1748917798 Timestamp [UCT]: 2025-06-03 02:29:58 Age [y:d:h:m:s]: 00:165:22:16:58
Block: 1296759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116267 RingCT/type: yes/0
Extra: 01121e716b649c31616a34ec339a13bfcd359a3c43a85bb809e83c0852b75d7bbc021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd08fcf62caf646764d4b00d83895860385a5f874f1da5a6295491bc2bb936c4 0.600000000000 1784274 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": 1296769, "vin": [ { "gen": { "height": 1296759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd08fcf62caf646764d4b00d83895860385a5f874f1da5a6295491bc2bb936c4" } } ], "extra": [ 1, 18, 30, 113, 107, 100, 156, 49, 97, 106, 52, 236, 51, 154, 19, 191, 205, 53, 154, 60, 67, 168, 91, 184, 9, 232, 60, 8, 82, 183, 93, 123, 188, 2, 17, 0, 0, 0, 5, 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