Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c21d90385fd3a957d0e9a227e80e3a680f4fbd4e74171e8256368403d1acf05a

Tx prefix hash: d799f16710ce4c42accdfe1e3ecfdecec527a72635fb37820dd1e80a3183e7d7
Tx public key: b82c9dbccabc19e48b93d3234af2801c5de63e207aee61f825e72033a5e28934
Timestamp: 1725112659 Timestamp [UCT]: 2024-08-31 13:57:39 Age [y:d:h:m:s]: 00:084:08:42:50
Block: 1099937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60336 RingCT/type: yes/0
Extra: 01b82c9dbccabc19e48b93d3234af2801c5de63e207aee61f825e72033a5e2893402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bfdcbfa396dd71d09afbbdb988e3c5c52bc1c4790f069e8b22399db8be1686f 0.600000000000 1575906 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": 1099947, "vin": [ { "gen": { "height": 1099937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bfdcbfa396dd71d09afbbdb988e3c5c52bc1c4790f069e8b22399db8be1686f" } } ], "extra": [ 1, 184, 44, 157, 188, 202, 188, 25, 228, 139, 147, 211, 35, 74, 242, 128, 28, 93, 230, 62, 32, 122, 238, 97, 248, 37, 231, 32, 51, 165, 226, 137, 52, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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