Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0350b9a1b0aae48da6bc1cc5f6c8b1e0f9c5114f9804ec81fe3b7f7838706021

Tx prefix hash: d0059d2773b8f09ed95142e17f1d2140fafc24c0ad422fb1fdc163234c6770ec
Tx public key: b2f4e81d71e10f92d6cf9a648ae8dc0775cfd6d2eed098437de286b017142242
Timestamp: 1580778859 Timestamp [UCT]: 2020-02-04 01:14:19 Age [y:d:h:m:s]: 05:040:11:21:45
Block: 57969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181163 RingCT/type: yes/0
Extra: 01b2f4e81d71e10f92d6cf9a648ae8dc0775cfd6d2eed098437de286b01714224202110000000a4943cd9f000000000000000000

1 output(s) for total of 394.389605536000 dcy

stealth address amount amount idx
00: 97f5ec7801012a084228918492a992ca0971e77d8ebaefc0a2dc9d5c3fac5426 394.389605536000 107220 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": 57979, "vin": [ { "gen": { "height": 57969 } } ], "vout": [ { "amount": 394389605536, "target": { "key": "97f5ec7801012a084228918492a992ca0971e77d8ebaefc0a2dc9d5c3fac5426" } } ], "extra": [ 1, 178, 244, 232, 29, 113, 225, 15, 146, 214, 207, 154, 100, 138, 232, 220, 7, 117, 207, 214, 210, 238, 208, 152, 67, 125, 226, 134, 176, 23, 20, 34, 66, 2, 17, 0, 0, 0, 10, 73, 67, 205, 159, 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