Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33bcef52cc7e7005630b69fd0f5ea53b38158d119ba1ef4ee362af9defb7897c

Tx prefix hash: 0d0ef808a7ce13d3f98dcb6d9737139d59118395e8d7a5ec7c08576ad5a54999
Tx public key: 7b4a5dbbadbe5916659eb1da679c26483c2e199c41ddb5d902cc27754dc7a9d7
Timestamp: 1724376413 Timestamp [UCT]: 2024-08-23 01:26:53 Age [y:d:h:m:s]: 00:217:05:25:16
Block: 1093853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155091 RingCT/type: yes/0
Extra: 017b4a5dbbadbe5916659eb1da679c26483c2e199c41ddb5d902cc27754dc7a9d7021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0beb8d071c133fd3b1bdb8c57c2615be7652de216932b057046d64af2cb58086 0.600000000000 1568880 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": 1093863, "vin": [ { "gen": { "height": 1093853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0beb8d071c133fd3b1bdb8c57c2615be7652de216932b057046d64af2cb58086" } } ], "extra": [ 1, 123, 74, 93, 187, 173, 190, 89, 22, 101, 158, 177, 218, 103, 156, 38, 72, 60, 46, 25, 156, 65, 221, 181, 217, 2, 204, 39, 117, 77, 199, 169, 215, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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