Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2afacc8ee8aad99cfcdbc5331724da5d2e59a29e558b8a03c1b97e06e7b4a21

Tx prefix hash: 526474ffe67b4f8ac609141b0f83a7b28f0bc09bdc408fbf5494459ae210e690
Tx public key: 8e8c0c4ae3034a65d958ea241da04284daf54dcae30fcb6001c57a926221d750
Timestamp: 1715835546 Timestamp [UCT]: 2024-05-16 04:59:06 Age [y:d:h:m:s]: 00:304:18:37:53
Block: 1023039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217845 RingCT/type: yes/0
Extra: 018e8c0c4ae3034a65d958ea241da04284daf54dcae30fcb6001c57a926221d7500211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f75d58d28bf1ee29dc19d0961a6b7f68ad8c59ff985c9034ac79580f11577dc5 0.600000000000 1487814 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": 1023049, "vin": [ { "gen": { "height": 1023039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f75d58d28bf1ee29dc19d0961a6b7f68ad8c59ff985c9034ac79580f11577dc5" } } ], "extra": [ 1, 142, 140, 12, 74, 227, 3, 74, 101, 217, 88, 234, 36, 29, 160, 66, 132, 218, 245, 77, 202, 227, 15, 203, 96, 1, 197, 122, 146, 98, 33, 215, 80, 2, 17, 0, 0, 0, 2, 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