Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7af79d507895d4c426dae3dd31b76176b14eda15970b58dbe80adfeb66d042a

Tx prefix hash: 639163cadc55f09a3fa79afdabbf81014cfc8c1d6ddfa83ba273c577f8e57c72
Tx public key: c543fd1c8205c07a1cae04f6fd881c71a3d9cfd198e937e462728abb32b0504c
Timestamp: 1580481428 Timestamp [UCT]: 2020-01-31 14:37:08 Age [y:d:h:m:s]: 04:330:18:10:26
Block: 55870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127606 RingCT/type: yes/0
Extra: 01c543fd1c8205c07a1cae04f6fd881c71a3d9cfd198e937e462728abb32b0504c021100000001dcee4b4d000000000000000000

1 output(s) for total of 400.756266164000 dcy

stealth address amount amount idx
00: 33ab74a4cbb60ae2df52ec5e7a41e352e27dc2682749396f2aea2f887be510db 400.756266164000 103064 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": 55880, "vin": [ { "gen": { "height": 55870 } } ], "vout": [ { "amount": 400756266164, "target": { "key": "33ab74a4cbb60ae2df52ec5e7a41e352e27dc2682749396f2aea2f887be510db" } } ], "extra": [ 1, 197, 67, 253, 28, 130, 5, 192, 122, 28, 174, 4, 246, 253, 136, 28, 113, 163, 217, 207, 209, 152, 233, 55, 228, 98, 114, 138, 187, 50, 176, 80, 76, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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