Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e896c42f3f1a23c45b335a82e4ba182994b723c83851319f33ec16c8b037001

Tx prefix hash: 9e6f7256c5db1f921dbda640c12611607ead53878adca17411d7f3d65b5513c5
Tx public key: f7e74b6f1a880720bd02040fe9441b875d2aa7ecdac1b18431c5571edba1eebb
Timestamp: 1708040248 Timestamp [UCT]: 2024-02-15 23:37:28 Age [y:d:h:m:s]: 01:309:20:23:12
Block: 958399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480262 RingCT/type: yes/0
Extra: 01f7e74b6f1a880720bd02040fe9441b875d2aa7ecdac1b18431c5571edba1eebb0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8c67eccfe26000e3c9187e948e026cb19f33d9123cbe4db639622a5806671da 0.600000000000 1417758 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": 958409, "vin": [ { "gen": { "height": 958399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8c67eccfe26000e3c9187e948e026cb19f33d9123cbe4db639622a5806671da" } } ], "extra": [ 1, 247, 231, 75, 111, 26, 136, 7, 32, 189, 2, 4, 15, 233, 68, 27, 135, 93, 42, 167, 236, 218, 193, 177, 132, 49, 197, 87, 30, 219, 161, 238, 187, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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