Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e67648a7a49f2baa0bb032e80cc52d8b20174640a74d202c3018c0a1d701020f

Tx prefix hash: d407a5d11c6cf7016390d1b5febc4915f523f31405e2378dfe825faa3103df71
Tx public key: d970f5387c3bc17be79092c5fc1a8628e9a0df14f00e83a09a1767db28ad1547
Timestamp: 1747698559 Timestamp [UCT]: 2025-05-19 23:49:19 Age [y:d:h:m:s]: 00:185:23:22:56
Block: 1286651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130616 RingCT/type: yes/0
Extra: 01d970f5387c3bc17be79092c5fc1a8628e9a0df14f00e83a09a1767db28ad15470211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15047c3b566a821bb97b2220f5e283a5c9daf4a172c331e34339d41d4a1c556b 0.600000000000 1774118 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": 1286661, "vin": [ { "gen": { "height": 1286651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15047c3b566a821bb97b2220f5e283a5c9daf4a172c331e34339d41d4a1c556b" } } ], "extra": [ 1, 217, 112, 245, 56, 124, 59, 193, 123, 231, 144, 146, 197, 252, 26, 134, 40, 233, 160, 223, 20, 240, 14, 131, 160, 154, 23, 103, 219, 40, 173, 21, 71, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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