Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77743de8324792e76799d6ebe75af0aa71dcbf107fa183eed341a33a981633fa

Tx prefix hash: fc36e3e62728221beb64ee5d560d626f6e1b330ef7ca503f83c9dfd737639b4d
Tx public key: 34d190aabbc397c4c31fd1abaf7eea3a16803e9f462f9c021e87eb5a335ed31b
Timestamp: 1702203306 Timestamp [UCT]: 2023-12-10 10:15:06 Age [y:d:h:m:s]: 01:048:20:00:18
Block: 910014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296033 RingCT/type: yes/0
Extra: 0134d190aabbc397c4c31fd1abaf7eea3a16803e9f462f9c021e87eb5a335ed31b021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a13130450c6b87a4cc9c491e751570fb44680a0727895a2fc4b5c6c541364ae1 0.600000000000 1367153 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": 910024, "vin": [ { "gen": { "height": 910014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a13130450c6b87a4cc9c491e751570fb44680a0727895a2fc4b5c6c541364ae1" } } ], "extra": [ 1, 52, 209, 144, 170, 187, 195, 151, 196, 195, 31, 209, 171, 175, 126, 234, 58, 22, 128, 62, 159, 70, 47, 156, 2, 30, 135, 235, 90, 51, 94, 211, 27, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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