Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e266814ada4c5579aed2a9990c34ae4503597dc43bb59f422830f7b78130d386

Tx prefix hash: bf932633b516513ccc068609b869401b91cea0bdc9143b129b436ec6e3522684
Tx public key: b8a345e87001c2968ef4d5beea1aa8d118b8160c137cb16e40fe69759ae06502
Timestamp: 1580694515 Timestamp [UCT]: 2020-02-03 01:48:35 Age [y:d:h:m:s]: 04:334:05:41:17
Block: 57421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130300 RingCT/type: yes/0
Extra: 01b8a345e87001c2968ef4d5beea1aa8d118b8160c137cb16e40fe69759ae0650202110000001fb221b3d1000000000000000000

1 output(s) for total of 396.041970362000 dcy

stealth address amount amount idx
00: 91d7debb07f441da83fe0a98e83722122e0d7f2c810c9bfd272577d5cbfc27c2 396.041970362000 106141 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": 57431, "vin": [ { "gen": { "height": 57421 } } ], "vout": [ { "amount": 396041970362, "target": { "key": "91d7debb07f441da83fe0a98e83722122e0d7f2c810c9bfd272577d5cbfc27c2" } } ], "extra": [ 1, 184, 163, 69, 232, 112, 1, 194, 150, 142, 244, 213, 190, 234, 26, 168, 209, 24, 184, 22, 12, 19, 124, 177, 110, 64, 254, 105, 117, 154, 224, 101, 2, 2, 17, 0, 0, 0, 31, 178, 33, 179, 209, 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