Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 974c7603eba907c89830807e49b61bb3e7726a981e39a479c9941aa16a7fd451

Tx prefix hash: f89b5d0d9197070e3459d3b4a43de649ef24c7de413ea1d07809083ca9644d7f
Tx public key: cc17c02d8ea295a2da1d744bb3856ccfb19427810f6c7b653f12a3b1a4ba02ca
Timestamp: 1719412689 Timestamp [UCT]: 2024-06-26 14:38:09 Age [y:d:h:m:s]: 01:219:23:43:03
Block: 1052683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415700 RingCT/type: yes/0
Extra: 01cc17c02d8ea295a2da1d744bb3856ccfb19427810f6c7b653f12a3b1a4ba02ca0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3205f3413a0a7db0e0ab2e6eb06ac14dc52236864498d37bd378bfd3cae42e80 0.600000000000 1523014 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": 1052693, "vin": [ { "gen": { "height": 1052683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3205f3413a0a7db0e0ab2e6eb06ac14dc52236864498d37bd378bfd3cae42e80" } } ], "extra": [ 1, 204, 23, 192, 45, 142, 162, 149, 162, 218, 29, 116, 75, 179, 133, 108, 207, 177, 148, 39, 129, 15, 108, 123, 101, 63, 18, 163, 177, 164, 186, 2, 202, 2, 17, 0, 0, 0, 1, 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