Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b022d89e47581163dd5f898231992dc82b7dbcf0389fe83dc4f35bc969694a7e

Tx prefix hash: c7af046972f1a4cb994d52629922a1699d32795b5e62c57d4fe0afe357d31c53
Tx public key: 8d6f22cc15c97568403c85da0a3cb6519e473f27750abf9d4e131637d3e67ec8
Timestamp: 1718089680 Timestamp [UCT]: 2024-06-11 07:08:00 Age [y:d:h:m:s]: 00:287:13:04:31
Block: 1041727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205463 RingCT/type: yes/0
Extra: 018d6f22cc15c97568403c85da0a3cb6519e473f27750abf9d4e131637d3e67ec80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59695bb8257b0de181522ff2b4de9b214e5e239f20108cddc923c68825d2663e 0.600000000000 1510472 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": 1041737, "vin": [ { "gen": { "height": 1041727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59695bb8257b0de181522ff2b4de9b214e5e239f20108cddc923c68825d2663e" } } ], "extra": [ 1, 141, 111, 34, 204, 21, 201, 117, 104, 64, 60, 133, 218, 10, 60, 182, 81, 158, 71, 63, 39, 117, 10, 191, 157, 78, 19, 22, 55, 211, 230, 126, 200, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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