Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41364e2c6a24c901a6fe50ad610dd799e80ac8b5f384a6571f47712384ec6b4

Tx prefix hash: fc76e1c2db2b3b5fb7ea05304bf92b8b14c590a9054c9e6ee83414a399d1fcee
Tx public key: f0bf533c6b5d482376da99bfd429f8d3d6e6c0fec7eab016c8369333b4e62cef
Timestamp: 1766154442 Timestamp [UCT]: 2025-12-19 14:27:22 Age [y:d:h:m:s]: 00:017:09:28:41
Block: 1437067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12472 RingCT/type: yes/0
Extra: 01f0bf533c6b5d482376da99bfd429f8d3d6e6c0fec7eab016c8369333b4e62cef02110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8d3da9cb571fe86b12c0f3e437326ad4a94a696d6e0ddc5b99b2aef6c878c9e 0.600000000000 1925872 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": 1437077, "vin": [ { "gen": { "height": 1437067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8d3da9cb571fe86b12c0f3e437326ad4a94a696d6e0ddc5b99b2aef6c878c9e" } } ], "extra": [ 1, 240, 191, 83, 60, 107, 93, 72, 35, 118, 218, 153, 191, 212, 41, 248, 211, 214, 230, 192, 254, 199, 234, 176, 22, 200, 54, 147, 51, 180, 230, 44, 239, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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