Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea9fe949e3d90c4455250b596ba8becb53b6fb27a04ed7cc691c09c87f7ac21

Tx prefix hash: 1f6dfe30818ac9946a72fba8c0620ddfe15908a3c87e7ec454aaf55eaf225dcc
Tx public key: f96950b20edde6f65ea08a512dd8e541a9544a1d0c103d92c035e9b61ba7bcd2
Timestamp: 1697271270 Timestamp [UCT]: 2023-10-14 08:14:30 Age [y:d:h:m:s]: 01:174:08:03:33
Block: 869328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385625 RingCT/type: yes/0
Extra: 01f96950b20edde6f65ea08a512dd8e541a9544a1d0c103d92c035e9b61ba7bcd202110000000233af99f4000000000000000000

1 output(s) for total of 0.808268194000 dcy

stealth address amount amount idx
00: f11ff1b78167065c6b24843f251e400ca276ac9f58e0b3e964bec0f8bb09c77c 0.808268194000 1324169 of 0

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": 869338, "vin": [ { "gen": { "height": 869328 } } ], "vout": [ { "amount": 808268194, "target": { "key": "f11ff1b78167065c6b24843f251e400ca276ac9f58e0b3e964bec0f8bb09c77c" } } ], "extra": [ 1, 249, 105, 80, 178, 14, 221, 230, 246, 94, 160, 138, 81, 45, 216, 229, 65, 169, 84, 74, 29, 12, 16, 61, 146, 192, 53, 233, 182, 27, 167, 188, 210, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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