Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98fe9a39776a9a8893bf7d96cbe1c520e26a2f8d6a7fdc1c5205e02a5f860649

Tx prefix hash: 650e12fd9c04c004f6c62fab703fab1f92f4d06789a7339134bcba5a922194b5
Tx public key: ae7e3c56165cb0123bf46385c5411301fd6447628b2b66dac35cc05bcaeb856b
Timestamp: 1738189587 Timestamp [UCT]: 2025-01-29 22:26:27 Age [y:d:h:m:s]: 00:295:09:18:23
Block: 1207935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208864 RingCT/type: yes/0
Extra: 01ae7e3c56165cb0123bf46385c5411301fd6447628b2b66dac35cc05bcaeb856b0211000000058368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f25475657774c77b18fa4327d2c8f1f2d179fd67b5f9bba31427e2d243bc8e35 0.600000000000 1694662 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": 1207945, "vin": [ { "gen": { "height": 1207935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f25475657774c77b18fa4327d2c8f1f2d179fd67b5f9bba31427e2d243bc8e35" } } ], "extra": [ 1, 174, 126, 60, 86, 22, 92, 176, 18, 59, 244, 99, 133, 197, 65, 19, 1, 253, 100, 71, 98, 139, 43, 102, 218, 195, 92, 192, 91, 202, 235, 133, 107, 2, 17, 0, 0, 0, 5, 131, 104, 38, 109, 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