Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17018f71694e6ba087522793672b0ffb9f65f19b014e3868b933d3d3dc0ce6db

Tx prefix hash: 936d1862e351ebf4470933a7cab1acc12106a543568c53bd7fa55b6d63957069
Tx public key: e9640c331e409288a443710b7184f653f4f97f17694628e690e52bb3c29fb1c0
Timestamp: 1618764910 Timestamp [UCT]: 2021-04-18 16:55:10 Age [y:d:h:m:s]: 03:294:03:33:26
Block: 242662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 970205 RingCT/type: yes/0
Extra: 01e9640c331e409288a443710b7184f653f4f97f17694628e690e52bb3c29fb1c002110000007190ec05ad000000000000000000

1 output(s) for total of 96.374164161000 dcy

stealth address amount amount idx
00: 9584fbc22c5c172e6642aff369e50946fd1eb33f24e892d979a3fe116d2a873e 96.374164161000 506166 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": 242672, "vin": [ { "gen": { "height": 242662 } } ], "vout": [ { "amount": 96374164161, "target": { "key": "9584fbc22c5c172e6642aff369e50946fd1eb33f24e892d979a3fe116d2a873e" } } ], "extra": [ 1, 233, 100, 12, 51, 30, 64, 146, 136, 164, 67, 113, 11, 113, 132, 246, 83, 244, 249, 127, 23, 105, 70, 40, 230, 144, 229, 43, 179, 194, 159, 177, 192, 2, 17, 0, 0, 0, 113, 144, 236, 5, 173, 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