Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e1d85e0ba462b747c6c0657440d4ab7499c9c0a412c8d7fb46403a5572ed740

Tx prefix hash: baa10569f921df8ac73cd78fee595710db2d6bfd4f3e642ab53636a7089a9db5
Tx public key: 5a4ba4f8fb97b524a871964312b01de6ed6eba19219d38ec37ff8fde8bc551d9
Timestamp: 1705202708 Timestamp [UCT]: 2024-01-14 03:25:08 Age [y:d:h:m:s]: 01:090:04:58:18
Block: 934856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325587 RingCT/type: yes/0
Extra: 015a4ba4f8fb97b524a871964312b01de6ed6eba19219d38ec37ff8fde8bc551d90211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9716aa5be96cfde8a4ee873eeee1b6d9cd994da9b731dcc50d302864dec1625e 0.600000000000 1392872 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": 934866, "vin": [ { "gen": { "height": 934856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9716aa5be96cfde8a4ee873eeee1b6d9cd994da9b731dcc50d302864dec1625e" } } ], "extra": [ 1, 90, 75, 164, 248, 251, 151, 181, 36, 168, 113, 150, 67, 18, 176, 29, 230, 237, 110, 186, 25, 33, 157, 56, 236, 55, 255, 143, 222, 139, 197, 81, 217, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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