Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f4ed41c5ca3a58671b1465c6b8b4403cb7e3e423c020072a032e3d11ad7fa54

Tx prefix hash: a38c3066305699162df522c443951a81774f1558d24250dc0cdc096a89696081
Tx public key: d9e07f65f38121e62aa21be141b72ce08a40231422d3ed100de5d675e7622b77
Timestamp: 1694261344 Timestamp [UCT]: 2023-09-09 12:09:04 Age [y:d:h:m:s]: 02:056:13:32:30
Block: 844350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560110 RingCT/type: yes/0
Extra: 01d9e07f65f38121e62aa21be141b72ce08a40231422d3ed100de5d675e7622b7702110000000275e3f0e9000000000000000000

1 output(s) for total of 0.977953057000 dcy

stealth address amount amount idx
00: 14e1a9a3d6a8712f8d6546be61ef2847d996ef975c05bb8ce80e8d44db42b808 0.977953057000 1297652 of 0

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": 844360, "vin": [ { "gen": { "height": 844350 } } ], "vout": [ { "amount": 977953057, "target": { "key": "14e1a9a3d6a8712f8d6546be61ef2847d996ef975c05bb8ce80e8d44db42b808" } } ], "extra": [ 1, 217, 224, 127, 101, 243, 129, 33, 230, 42, 162, 27, 225, 65, 183, 44, 224, 138, 64, 35, 20, 34, 211, 237, 16, 13, 229, 214, 117, 231, 98, 43, 119, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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