Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d8dc8fecb6d64ad78aabc062b6a156e9d607ef759f68f48e09701f8c64b3346

Tx prefix hash: 65d777cd795d6a710ddc99934972b0daefcd873fda569f7d671e235de20fd7f8
Tx public key: bee34cdef3f479e4b1e7b522300b87571a3656db2e51b579f4e8ecd40710a074
Timestamp: 1762807888 Timestamp [UCT]: 2025-11-10 20:51:28 Age [y:d:h:m:s]: 00:078:13:03:38
Block: 1409327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56063 RingCT/type: yes/0
Extra: 01bee34cdef3f479e4b1e7b522300b87571a3656db2e51b579f4e8ecd40710a07402110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b2eb14e7eeb9098445b5b39ccfcd3c5e597789326bef59c033be88a03b71e04 0.600000000000 1897772 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": 1409337, "vin": [ { "gen": { "height": 1409327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b2eb14e7eeb9098445b5b39ccfcd3c5e597789326bef59c033be88a03b71e04" } } ], "extra": [ 1, 190, 227, 76, 222, 243, 244, 121, 228, 177, 231, 181, 34, 48, 11, 135, 87, 26, 54, 86, 219, 46, 81, 181, 121, 244, 232, 236, 212, 7, 16, 160, 116, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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