Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 424dd9da414572779cd2531b96ffb5a4f5b6fe4148dfc48a212e0fef44a8202c

Tx prefix hash: 6dce6302038d610b8b0fbddbeaf3e0cc489a4d5390383d06acf15b910b1e68aa
Tx public key: 01d7538b11e9cbc04335c1f7abe2713dfa481e0c5012d2b0e2f683603d1c8937
Timestamp: 1669657697 Timestamp [UCT]: 2022-11-28 17:48:17 Age [y:d:h:m:s]: 02:179:01:30:06
Block: 641096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649721 RingCT/type: yes/0
Extra: 0101d7538b11e9cbc04335c1f7abe2713dfa481e0c5012d2b0e2f683603d1c8937021100000001272bcc39000000000000000000

1 output(s) for total of 4.610869386000 dcy

stealth address amount amount idx
00: 65b41a22ba14f1ddb4aedf68b6cd47405127a6a60fe1d8fd31adf5fb58cafbe0 4.610869386000 1080871 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": 641106, "vin": [ { "gen": { "height": 641096 } } ], "vout": [ { "amount": 4610869386, "target": { "key": "65b41a22ba14f1ddb4aedf68b6cd47405127a6a60fe1d8fd31adf5fb58cafbe0" } } ], "extra": [ 1, 1, 215, 83, 139, 17, 233, 203, 192, 67, 53, 193, 247, 171, 226, 113, 61, 250, 72, 30, 12, 80, 18, 210, 176, 226, 246, 131, 96, 61, 28, 137, 55, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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