Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ef2c24f017a7482a283236e1ae6746f99e7641c12495537ea1c0dfa76901237

Tx prefix hash: 8721eb4d13d6459b0ce9ea679a4d822194557f32af602cb87a241610d3b2afdb
Tx public key: 91622e100f2949d22a9c0532929c6e99bf51d20a430384d0ebc18bc47b4ae2af
Timestamp: 1702585169 Timestamp [UCT]: 2023-12-14 20:19:29 Age [y:d:h:m:s]: 01:153:15:36:14
Block: 913168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370981 RingCT/type: yes/0
Extra: 0191622e100f2949d22a9c0532929c6e99bf51d20a430384d0ebc18bc47b4ae2af02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75e79ee943eb505cd94afb5ffdb201c2dd95b3a02329ce883f0fa902a8cd3ada 0.600000000000 1370414 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": 913178, "vin": [ { "gen": { "height": 913168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75e79ee943eb505cd94afb5ffdb201c2dd95b3a02329ce883f0fa902a8cd3ada" } } ], "extra": [ 1, 145, 98, 46, 16, 15, 41, 73, 210, 42, 156, 5, 50, 146, 156, 110, 153, 191, 81, 210, 10, 67, 3, 132, 208, 235, 193, 139, 196, 123, 74, 226, 175, 2, 17, 0, 0, 0, 5, 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