Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41b3d35cf71061fe861df3e165082fd81912b2525542a7bd984dad1a597f41b9

Tx prefix hash: 66bea00d1cae712a5577c3d5ac1e804dc68a6c88323e14f45acb7d13301e0a4c
Tx public key: c72fe88d130910d560f26f8e7688ee4c438ca1da0198e7feb5eb3d35d858f358
Timestamp: 1708624734 Timestamp [UCT]: 2024-02-22 17:58:54 Age [y:d:h:m:s]: 01:048:13:34:59
Block: 963245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295744 RingCT/type: yes/0
Extra: 01c72fe88d130910d560f26f8e7688ee4c438ca1da0198e7feb5eb3d35d858f3580211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23d56382b76e103a0f644116ccd92813e21f8ec42897823d609e8a5166e3398c 0.600000000000 1422946 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": 963255, "vin": [ { "gen": { "height": 963245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23d56382b76e103a0f644116ccd92813e21f8ec42897823d609e8a5166e3398c" } } ], "extra": [ 1, 199, 47, 232, 141, 19, 9, 16, 213, 96, 242, 111, 142, 118, 136, 238, 76, 67, 140, 161, 218, 1, 152, 231, 254, 181, 235, 61, 53, 216, 88, 243, 88, 2, 17, 0, 0, 0, 2, 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