Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 202b607ffa7b1fe0dca716a88314af3dbf88bd0b8d9612c13351d8534a2c93aa

Tx prefix hash: f5b28c262e556e9ef7076e83430dae4582e93bf8c4aba0f321818b90a729d49c
Tx public key: 57919efcd1d08488bdee76fe22628de32399e185b50b8b65402bccc061fd2dd5
Timestamp: 1673083950 Timestamp [UCT]: 2023-01-07 09:32:30 Age [y:d:h:m:s]: 02:011:20:04:11
Block: 669450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530385 RingCT/type: yes/0
Extra: 0157919efcd1d08488bdee76fe22628de32399e185b50b8b65402bccc061fd2dd502110000000152542ceb000000000000000000

1 output(s) for total of 3.713934209000 dcy

stealth address amount amount idx
00: 0fa0ac23ab1d09c41037c38ace7ed13b7a14e2218a85e9cf1a35c45dde9d60c0 3.713934209000 1110767 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": 669460, "vin": [ { "gen": { "height": 669450 } } ], "vout": [ { "amount": 3713934209, "target": { "key": "0fa0ac23ab1d09c41037c38ace7ed13b7a14e2218a85e9cf1a35c45dde9d60c0" } } ], "extra": [ 1, 87, 145, 158, 252, 209, 208, 132, 136, 189, 238, 118, 254, 34, 98, 141, 227, 35, 153, 225, 133, 181, 11, 139, 101, 64, 43, 204, 192, 97, 253, 45, 213, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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