Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a3c93461fe049c245861608a5ab1125aeb0f065c0a5ccf5f069a2f1712809f6

Tx prefix hash: 2bca07e12f7a3be23271b313ebaf0d634d72afb619b17e5805c4d9f06d8af6eb
Tx public key: ab04b7dd678981711aa4044e8ac5345e0fe7471d4b98dda81fcf3e645c5320db
Timestamp: 1711348903 Timestamp [UCT]: 2024-03-25 06:41:43 Age [y:d:h:m:s]: 01:060:17:42:19
Block: 985855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304401 RingCT/type: yes/0
Extra: 01ab04b7dd678981711aa4044e8ac5345e0fe7471d4b98dda81fcf3e645c5320db02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35f0a64675635b1a73048dc5b53cbacc493b8134500955da2e604df32a18303f 0.600000000000 1446076 of 15

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": 985865, "vin": [ { "gen": { "height": 985855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35f0a64675635b1a73048dc5b53cbacc493b8134500955da2e604df32a18303f" } } ], "extra": [ 1, 171, 4, 183, 221, 103, 137, 129, 113, 26, 164, 4, 78, 138, 197, 52, 94, 15, 231, 71, 29, 75, 152, 221, 168, 31, 207, 62, 100, 92, 83, 32, 219, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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