Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1725bcddcab83972d42e24c8a629776ecaf76b18d6417de07b2622d2050641f7

Tx prefix hash: b22bafb29763c2c40d809dfd3146518849b891b7a5943318fd60ca5e9538e6e3
Tx public key: f01db9aa208f405b0b4ac94d961c1c86608e9f268547b842ba70ed94310509c4
Timestamp: 1730097537 Timestamp [UCT]: 2024-10-28 06:38:57 Age [y:d:h:m:s]: 00:157:19:40:12
Block: 1141191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112619 RingCT/type: yes/0
Extra: 01f01db9aa208f405b0b4ac94d961c1c86608e9f268547b842ba70ed94310509c4021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ca2bdfb76887657a21e0b65b26929d1ec27e78a1efafc633928282c34fcc8af 0.600000000000 1624998 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": 1141201, "vin": [ { "gen": { "height": 1141191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ca2bdfb76887657a21e0b65b26929d1ec27e78a1efafc633928282c34fcc8af" } } ], "extra": [ 1, 240, 29, 185, 170, 32, 143, 64, 91, 11, 74, 201, 77, 150, 28, 28, 134, 96, 142, 159, 38, 133, 71, 184, 66, 186, 112, 237, 148, 49, 5, 9, 196, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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