← previous blocknext block →recent activity
Analyzing
Block #83,903,618
20 transactions · 20 stateful · 2026-06-26 22:12:03 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,903,618 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w29w310w411w512w613w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc111d09…525a
0x336ed4…c59c
14 touches
21 conflicts
0x00000000…000b
0x90c374…be45
14 touches
21 conflicts
0x00000000…000a
0x90c374…be45
14 touches
21 conflicts
0x655939a8…0b3b
0x336ed4…c59c
14 touches
21 conflicts
0x659bf1d4…2024
0x336ed4…c59c
14 touches
21 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21bf
0x1b6862…e19c
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x336ed437…cfc59c
21 conflicts on slot 0xfc111d09a6…d6525a
Audit this contract →
← previous block·next block →recent activity