Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16299e539887c3a7f18c00f8361386919425c4435afc37dd3edb7a214f4b7ab3

Tx prefix hash: 383e6300853af9f46dd2fd2244cd60657bd87fc79425a232163853cf2c454a6b
Tx public key: ccf9bed095cf4fdc1a515bfca7cae3a33fce1265ad903973b8d94ce9aa831cfe
Timestamp: 1700287776 Timestamp [UCT]: 2023-11-18 06:09:36 Age [y:d:h:m:s]: 01:131:07:55:58
Block: 894127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355039 RingCT/type: yes/0
Extra: 01ccf9bed095cf4fdc1a515bfca7cae3a33fce1265ad903973b8d94ce9aa831cfe02110000000933af99f4000000000000000000

1 output(s) for total of 0.668938314000 dcy

stealth address amount amount idx
00: 34b33eb81092a6f2df49e58ed78dde20d87d5e35126f3bf395999528433add37 0.668938314000 1350318 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": 894137, "vin": [ { "gen": { "height": 894127 } } ], "vout": [ { "amount": 668938314, "target": { "key": "34b33eb81092a6f2df49e58ed78dde20d87d5e35126f3bf395999528433add37" } } ], "extra": [ 1, 204, 249, 190, 208, 149, 207, 79, 220, 26, 81, 91, 252, 167, 202, 227, 163, 63, 206, 18, 101, 173, 144, 57, 115, 184, 217, 76, 233, 170, 131, 28, 254, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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