Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4fe9a6a57cf45da488b87a98ed70ab22f3ce0b2f44e6014b05e4cec08bcc99a

Tx prefix hash: 21f82456cfb0b7516785d4202b62e28af8d0e899fe47509592e4243824cd6061
Tx public key: 7785f63c4abb9528a4008ff2e8956d095a411aa7e756ffdce727ac89d4ead6dc
Timestamp: 1704240581 Timestamp [UCT]: 2024-01-03 00:09:41 Age [y:d:h:m:s]: 01:078:20:14:38
Block: 926893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317460 RingCT/type: yes/0
Extra: 017785f63c4abb9528a4008ff2e8956d095a411aa7e756ffdce727ac89d4ead6dc0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29bf91f8f7260cddc6e07abf4bf60266060ce11d3aed51a798dbb77c306efbd0 0.600000000000 1384693 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": 926903, "vin": [ { "gen": { "height": 926893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29bf91f8f7260cddc6e07abf4bf60266060ce11d3aed51a798dbb77c306efbd0" } } ], "extra": [ 1, 119, 133, 246, 60, 74, 187, 149, 40, 164, 0, 143, 242, 232, 149, 109, 9, 90, 65, 26, 167, 231, 86, 255, 220, 231, 39, 172, 137, 212, 234, 214, 220, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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