Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f8b9231521abe29ae0066f8fc99d6eb7fe26ec3d62f2bf97f7309e7129411f

Tx prefix hash: 15ffa6a7c96b913c9d3897a5fbf7ae423b8ad1435767cf0ebb2b2dec1edb172d
Tx public key: c728a95e8592b03506d3bf7901f0f4179a46100db19967565d8802d60b516fdc
Timestamp: 1717461701 Timestamp [UCT]: 2024-06-04 00:41:41 Age [y:d:h:m:s]: 01:155:05:51:58
Block: 1036518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369507 RingCT/type: yes/0
Extra: 01c728a95e8592b03506d3bf7901f0f4179a46100db19967565d8802d60b516fdc0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4ff96c940fb582f91bd2bbce4cc82ff7287bfc156afd8b461a765096b242e8c 0.600000000000 1505045 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": 1036528, "vin": [ { "gen": { "height": 1036518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4ff96c940fb582f91bd2bbce4cc82ff7287bfc156afd8b461a765096b242e8c" } } ], "extra": [ 1, 199, 40, 169, 94, 133, 146, 176, 53, 6, 211, 191, 121, 1, 240, 244, 23, 154, 70, 16, 13, 177, 153, 103, 86, 93, 136, 2, 214, 11, 81, 111, 220, 2, 17, 0, 0, 0, 6, 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