Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d716ceb1e0d10ef6ea65384540b8a9c6d115bd0aa93ec922c3a9641570d4014d

Tx prefix hash: 932e6a40769bcd8b281e1b20956d4ee3eeab708246a16dc028c1f7f70c3b3cc0
Tx public key: c64df0c51a79e2c0614103cc1bb7fc76c04692586f45344ebd6adab7f1d7fe3b
Timestamp: 1656959372 Timestamp [UCT]: 2022-07-04 18:29:32 Age [y:d:h:m:s]: 03:120:03:01:29
Block: 536638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 865556 RingCT/type: yes/0
Extra: 01c64df0c51a79e2c0614103cc1bb7fc76c04692586f45344ebd6adab7f1d7fe3b021100000001cb8520c2000000000000000000

1 output(s) for total of 10.230472418000 dcy

stealth address amount amount idx
00: 19a212248979db87d59232efb49e9edfea037f0ddf361aa8a07bd15fecda1034 10.230472418000 966423 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": 536648, "vin": [ { "gen": { "height": 536638 } } ], "vout": [ { "amount": 10230472418, "target": { "key": "19a212248979db87d59232efb49e9edfea037f0ddf361aa8a07bd15fecda1034" } } ], "extra": [ 1, 198, 77, 240, 197, 26, 121, 226, 192, 97, 65, 3, 204, 27, 183, 252, 118, 192, 70, 146, 88, 111, 69, 52, 78, 189, 106, 218, 183, 241, 215, 254, 59, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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