Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 467d3a6b5537900630474e98c74abe469b111ecc5330a948eaf1cecdb9c40ca1

Tx prefix hash: 9f84d4ddd2b8fb6cb29dbb39eae4a57947ac5277e87135f1474703ff2ee7c00c
Tx public key: 8fa0ef5f629fb713b5360c2db3779da1a803dad8992729fe9a8d46745994ab2b
Timestamp: 1669629782 Timestamp [UCT]: 2022-11-28 10:03:02 Age [y:d:h:m:s]: 02:090:23:47:04
Block: 640865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586703 RingCT/type: yes/0
Extra: 018fa0ef5f629fb713b5360c2db3779da1a803dad8992729fe9a8d46745994ab2b02110000000233af99f4000000000000000000

1 output(s) for total of 4.619002733000 dcy

stealth address amount amount idx
00: f97fbbaa9591745a8aedc0d458c4fe69754aee33513aebac910dacbd1d4a405f 4.619002733000 1080626 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": 640875, "vin": [ { "gen": { "height": 640865 } } ], "vout": [ { "amount": 4619002733, "target": { "key": "f97fbbaa9591745a8aedc0d458c4fe69754aee33513aebac910dacbd1d4a405f" } } ], "extra": [ 1, 143, 160, 239, 95, 98, 159, 183, 19, 181, 54, 12, 45, 179, 119, 157, 161, 168, 3, 218, 216, 153, 39, 41, 254, 154, 141, 70, 116, 89, 148, 171, 43, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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