← previous blocknext block →recent activity
Analyzing
Block #93,675,936
21 transactions · 20 stateful · 2026-08-06 16:02:01 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.95
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,675,936 · 21 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
1w02w13w04w15w06w17w08w19w210w211w214w115w316w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b9bb4b…145a
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6a87657b…82b4
0xd32edf…ff58
5 touches
3 conflicts
0x2e2d9f89…e534
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xc6b9bb4b8d…cc145a
Audit this contract →
← previous block·next block →recent activity