Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b3b64857c285bb4e040f99ea0a1c6309e656285e08785af8236dba66264db61

Tx prefix hash: 8898406234e80aa1e4fa0eb2adf63bb435d5c523d3c6bf5d02094f3909fb6481
Tx public key: 22771eb75ef876d6084cb7d2d7ea9b2110c56e739dedf6f97fc40d7dcc95fc56
Timestamp: 1728714151 Timestamp [UCT]: 2024-10-12 06:22:31 Age [y:d:h:m:s]: 00:006:09:04:04
Block: 1129800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4567 RingCT/type: yes/0
Extra: 0122771eb75ef876d6084cb7d2d7ea9b2110c56e739dedf6f97fc40d7dcc95fc56021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 985ea9cdc4ac1a0ca930a99e87c5390fe5f17cefb417cb479d20096bd5c12d36 0.600000000000 1612661 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": 1129810, "vin": [ { "gen": { "height": 1129800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "985ea9cdc4ac1a0ca930a99e87c5390fe5f17cefb417cb479d20096bd5c12d36" } } ], "extra": [ 1, 34, 119, 30, 183, 94, 248, 118, 214, 8, 76, 183, 210, 215, 234, 155, 33, 16, 197, 110, 115, 157, 237, 246, 249, 127, 196, 13, 125, 204, 149, 252, 86, 2, 17, 0, 0, 0, 8, 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