Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 537eb1412e0b7e9f949dc82a4fc50e8a30c9c1f3242a3bfa9deeadb5af5cfdb4

Tx prefix hash: b9479a496ad5b50635cdd845f82cf1e86d0a62476b1269adca305f8f1a89d9c5
Tx public key: 8bcd23f0ad930927a6aeb886648119731d9f0d1524df1ddfbf567ae0c2866ade
Timestamp: 1736815877 Timestamp [UCT]: 2025-01-14 00:51:17 Age [y:d:h:m:s]: 00:157:06:43:32
Block: 1196823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112073 RingCT/type: yes/0
Extra: 018bcd23f0ad930927a6aeb886648119731d9f0d1524df1ddfbf567ae0c2866ade0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b9e2b8294cdeb940ed7b868400427de2aff71f37dd02d368872e0eec8425e33 0.600000000000 1683426 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": 1196833, "vin": [ { "gen": { "height": 1196823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b9e2b8294cdeb940ed7b868400427de2aff71f37dd02d368872e0eec8425e33" } } ], "extra": [ 1, 139, 205, 35, 240, 173, 147, 9, 39, 166, 174, 184, 134, 100, 129, 25, 115, 29, 159, 13, 21, 36, 223, 29, 223, 191, 86, 122, 224, 194, 134, 106, 222, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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