Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d18e11dd732300e035eaf48284a99ffc1cb1a8434502977d002a0d28f7abd7a

Tx prefix hash: af11fa08493fde3d80e3d58261fffa28a0f27e9cd5b790a2d6b787df0e89a4ac
Tx public key: b3942531bd4214187f2fe2128f04254ec123a016d564d35a2de98bfd658695dc
Timestamp: 1721250306 Timestamp [UCT]: 2024-07-17 21:05:06 Age [y:d:h:m:s]: 00:133:17:40:12
Block: 1067930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95696 RingCT/type: yes/0
Extra: 01b3942531bd4214187f2fe2128f04254ec123a016d564d35a2de98bfd658695dc02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0b0bf60a6be985a1f2a9d7c8ae83d847f53300b7a1f519d9cc05c0a00b0c40d 0.600000000000 1538879 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": 1067940, "vin": [ { "gen": { "height": 1067930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0b0bf60a6be985a1f2a9d7c8ae83d847f53300b7a1f519d9cc05c0a00b0c40d" } } ], "extra": [ 1, 179, 148, 37, 49, 189, 66, 20, 24, 127, 47, 226, 18, 143, 4, 37, 78, 193, 35, 160, 22, 213, 100, 211, 90, 45, 233, 139, 253, 101, 134, 149, 220, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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