Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e2eed6e2800d0622baced6685488e7a03efedbc0db7104b9ae1bd7e966c85f

Tx prefix hash: e4c4422d4558ec471c9c6c59173ea8969b2016c2ba9df480104b75851849e88c
Tx public key: c86d5510718ed6f83fe728c9083d9bd089d4f705d9a6d7aee36e48e4d464ab75
Timestamp: 1749044714 Timestamp [UCT]: 2025-06-04 13:45:14 Age [y:d:h:m:s]: 00:164:14:48:56
Block: 1297823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115316 RingCT/type: yes/0
Extra: 01c86d5510718ed6f83fe728c9083d9bd089d4f705d9a6d7aee36e48e4d464ab7502110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f69d3712dec94278fe9fe76d0d1b12d5b0c2064c70357366d0de12f5b045104 0.600000000000 1785344 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": 1297833, "vin": [ { "gen": { "height": 1297823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f69d3712dec94278fe9fe76d0d1b12d5b0c2064c70357366d0de12f5b045104" } } ], "extra": [ 1, 200, 109, 85, 16, 113, 142, 214, 248, 63, 231, 40, 201, 8, 61, 155, 208, 137, 212, 247, 5, 217, 166, 215, 174, 227, 110, 72, 228, 212, 100, 171, 117, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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