← previous blocknext block →recent activity
Analyzing
Block #94,842,847
23 transactions · 21 stateful · 2026-08-10 18:08:33 UTC
Parallelism
65/100
Blocked
62%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,842,847 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w06w19w211w312w413w514w616w518w619w220w321w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07c94816…b666
0x34b655…2a6f
8 touches
6 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
8 touches
6 conflicts
0x49a8c6dc…bb08
0xd32edf…ff58
7 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdbc6e634…e168
0x1b6862…e19c
4 touches
1 conflict
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
6 conflicts on slot 0x07c9481616…dab666
Audit this contract →
← previous block·next block →recent activity