Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a66591be06efceaf9246ac735717d223ca2d5df68bc4490d7c9f48974439a5b0

Tx prefix hash: 545ff3e6e9cdba354267b90d83a86315227b024a8c5cda5889e031840c5cd637
Tx public key: 1e4970e6f869caa9c49b92b12a0426329f52f44856d45e0b2a28748736a5eef9
Timestamp: 1763689803 Timestamp [UCT]: 2025-11-21 01:50:03 Age [y:d:h:m:s]: 00:072:12:26:29
Block: 1416623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51758 RingCT/type: yes/0
Extra: 011e4970e6f869caa9c49b92b12a0426329f52f44856d45e0b2a28748736a5eef90211000000017b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1bf4ca240f38bcdad099ac3909d80689fddebea3174a6df0c946cc4d0c0a88b 0.600000000000 1905142 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": 1416633, "vin": [ { "gen": { "height": 1416623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1bf4ca240f38bcdad099ac3909d80689fddebea3174a6df0c946cc4d0c0a88b" } } ], "extra": [ 1, 30, 73, 112, 230, 248, 105, 202, 169, 196, 155, 146, 177, 42, 4, 38, 50, 159, 82, 244, 72, 86, 212, 94, 11, 42, 40, 116, 135, 54, 165, 238, 249, 2, 17, 0, 0, 0, 1, 123, 30, 81, 172, 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