Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10889d1a966ca3d39be3c07b002b38752942a4ca7fb053027527dac7bae71387

Tx prefix hash: c60b91c02399806c5b1255b99e3b5c2021070a49c9343a7e1f419b67e05cd016
Tx public key: b3f67f78b89f2c2c41392f1b5c09d0fe550cda1d68d300e90f37888102ab3984
Timestamp: 1719200392 Timestamp [UCT]: 2024-06-24 03:39:52 Age [y:d:h:m:s]: 00:357:06:27:11
Block: 1050919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255244 RingCT/type: yes/0
Extra: 01b3f67f78b89f2c2c41392f1b5c09d0fe550cda1d68d300e90f37888102ab3984021100000003a6fba9af000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1629ebd9cc4ae4617735383b8aed8e4b9542fc2b748ee269ffa50616ed1727f1 0.600000000000 1521096 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": 1050929, "vin": [ { "gen": { "height": 1050919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1629ebd9cc4ae4617735383b8aed8e4b9542fc2b748ee269ffa50616ed1727f1" } } ], "extra": [ 1, 179, 246, 127, 120, 184, 159, 44, 44, 65, 57, 47, 27, 92, 9, 208, 254, 85, 12, 218, 29, 104, 211, 0, 233, 15, 55, 136, 129, 2, 171, 57, 132, 2, 17, 0, 0, 0, 3, 166, 251, 169, 175, 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