Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57515246591146b4274da24b3fc8800260870b049ef54447b5d95f6678bf177c

Tx prefix hash: ddc5c1adc586fe2ba5eb3f0bda4355956cba88413cf45ad15755b2c0f65cab9c
Tx public key: 081d1779c81dce100dc0c095a93cb82fa02745df6660b1e73411b2b12668d284
Timestamp: 1580701876 Timestamp [UCT]: 2020-02-03 03:51:16 Age [y:d:h:m:s]: 05:039:02:36:27
Block: 57670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1179826 RingCT/type: yes/0
Extra: 01081d1779c81dce100dc0c095a93cb82fa02745df6660b1e73411b2b12668d284021100000001b221b3d1000000000000000000

1 output(s) for total of 395.301473139000 dcy

stealth address amount amount idx
00: a7261e7dbfda86cb505e38db0cb95e2299a034dda83892ec22f2178e4e7571d4 395.301473139000 106583 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": 57680, "vin": [ { "gen": { "height": 57670 } } ], "vout": [ { "amount": 395301473139, "target": { "key": "a7261e7dbfda86cb505e38db0cb95e2299a034dda83892ec22f2178e4e7571d4" } } ], "extra": [ 1, 8, 29, 23, 121, 200, 29, 206, 16, 13, 192, 192, 149, 169, 60, 184, 47, 160, 39, 69, 223, 102, 96, 177, 231, 52, 17, 178, 177, 38, 104, 210, 132, 2, 17, 0, 0, 0, 1, 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