← previous blocknext block →recent activity
Analyzing
Block #93,675,110
20 transactions · 19 stateful · 2026-08-06 15:57:52 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,675,110 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w19w211w012w114w215w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7954a60…d294
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2f92e43a…44c3
0x34b655…2a6f
4 touches
1 conflict
0x47c9eddd…356d
0x34b655…2a6f
4 touches
1 conflict
0x4bc1abab…5874
0x34b655…2a6f
4 touches
1 conflict
0x4f024493…baf5
0x34b655…2a6f
4 touches
1 conflict
0x5e7e0120…7bb9
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
3 conflicts on slot 0xc7954a6095…b3d294
Audit this contract →
← previous block·next block →recent activity