Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16c5c66dafe8ed493bf61df51de60ee30ed20a338ed740265c74ccd0046246bc

Tx prefix hash: 07376ed9522e2bd4736df48d55d7759002df6043e63d11eb8b3e4b3fd0207a50
Tx public key: e284995d3c600e1ab4b8a1bd2e4692e6ba9afd9641e291303be0dd0bb8de5276
Timestamp: 1724756281 Timestamp [UCT]: 2024-08-27 10:58:01 Age [y:d:h:m:s]: 00:282:07:57:44
Block: 1096983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201687 RingCT/type: yes/0
Extra: 01e284995d3c600e1ab4b8a1bd2e4692e6ba9afd9641e291303be0dd0bb8de5276021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8706922b4a9fa8e436715f4f02f04913fcc29d4fbef33892ecfa5dbd6866c610 0.600000000000 1572232 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": 1096993, "vin": [ { "gen": { "height": 1096983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8706922b4a9fa8e436715f4f02f04913fcc29d4fbef33892ecfa5dbd6866c610" } } ], "extra": [ 1, 226, 132, 153, 93, 60, 96, 14, 26, 180, 184, 161, 189, 46, 70, 146, 230, 186, 154, 253, 150, 65, 226, 145, 48, 59, 224, 221, 11, 184, 222, 82, 118, 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