Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0588dcfe19770a38c8745ecd9f484badb16f4fa1a7cef4432767eed2ea12cf07

Tx prefix hash: a480f6686a1053315fd9ec60afe3596548183d7921c8fb9a6ead44133423735b
Tx public key: 7f22626ab7dee5f1705154f336d4d805d7df9be99a25e66f9c8bf4229f241a79
Timestamp: 1711384200 Timestamp [UCT]: 2024-03-25 16:30:00 Age [y:d:h:m:s]: 01:081:20:09:48
Block: 986151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319383 RingCT/type: yes/0
Extra: 017f22626ab7dee5f1705154f336d4d805d7df9be99a25e66f9c8bf4229f241a7902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf8b99a3c668104df8a1ae78795499d74f8f0f50a555048e186e08aab4f0c48b 0.600000000000 1446378 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": 986161, "vin": [ { "gen": { "height": 986151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf8b99a3c668104df8a1ae78795499d74f8f0f50a555048e186e08aab4f0c48b" } } ], "extra": [ 1, 127, 34, 98, 106, 183, 222, 229, 241, 112, 81, 84, 243, 54, 212, 216, 5, 215, 223, 155, 233, 154, 37, 230, 111, 156, 139, 244, 34, 159, 36, 26, 121, 2, 17, 0, 0, 0, 3, 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