Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39ca6a76fd210d1f94ce6d54b37487ff4c6c76cfe950bd8d2b04c9c2ba152667

Tx prefix hash: 58eda59ed24eede0b84514c674a6c3d7a10889368758c5236a236894ceff5e61
Tx public key: db961c0b41c3e5e46893912fed29ec4efbd5564dbd6d0fab55b8f5d76af50e1a
Timestamp: 1733567173 Timestamp [UCT]: 2024-12-07 10:26:13 Age [y:d:h:m:s]: 00:107:07:08:13
Block: 1169932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76472 RingCT/type: yes/0
Extra: 01db961c0b41c3e5e46893912fed29ec4efbd5564dbd6d0fab55b8f5d76af50e1a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18926a7ad20587786bd0d5fcffe4b4a9a36113b2e63ccbf696f7282a24209bce 0.600000000000 1655657 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": 1169942, "vin": [ { "gen": { "height": 1169932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18926a7ad20587786bd0d5fcffe4b4a9a36113b2e63ccbf696f7282a24209bce" } } ], "extra": [ 1, 219, 150, 28, 11, 65, 195, 229, 228, 104, 147, 145, 47, 237, 41, 236, 78, 251, 213, 86, 77, 189, 109, 15, 171, 85, 184, 245, 215, 106, 245, 14, 26, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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