Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90a1c6fed2d9696d50a455e463d775aa3b2abbdfa4167d43277ae04a52791fef

Tx prefix hash: 4974186130403796d99cebfbf1c32be9db6382bbd674709c16718fdf5169d6d1
Tx public key: 645122f0e5925b06b651b32cb9dd45b9a819f1b9de15571bd959cb390ae1a727
Timestamp: 1690174768 Timestamp [UCT]: 2023-07-24 04:59:28 Age [y:d:h:m:s]: 01:254:20:59:46
Block: 810560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443242 RingCT/type: yes/0
Extra: 01645122f0e5925b06b651b32cb9dd45b9a819f1b9de15571bd959cb390ae1a727021100000001faf35c9c000000000000000000

1 output(s) for total of 1.265547222000 dcy

stealth address amount amount idx
00: e72601d17ed97be95a12bd475c6ce04631dc79158696d3fb38b8090be526a136 1.265547222000 1262195 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": 810570, "vin": [ { "gen": { "height": 810560 } } ], "vout": [ { "amount": 1265547222, "target": { "key": "e72601d17ed97be95a12bd475c6ce04631dc79158696d3fb38b8090be526a136" } } ], "extra": [ 1, 100, 81, 34, 240, 229, 146, 91, 6, 182, 81, 179, 44, 185, 221, 69, 185, 168, 25, 241, 185, 222, 21, 87, 27, 217, 89, 203, 57, 10, 225, 167, 39, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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