← previous blocknext block →recent activity
Analyzing
Block #94,307,271
10 transactions · 9 stateful · 2026-08-08 21:04:40 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,307,271 · 10 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
1w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1279ed80…4a27
0x34b655…2a6f
6 touches
3 conflicts
0xe75060c3…b41e
0x34b655…2a6f
4 touches
1 conflict
0xec2ab287…49a3
0x34b655…2a6f
4 touches
1 conflict
0x28c9fead…e35b
0x34b655…2a6f
2 touches
0 conflicts
0x5142ff3f…6c11
0x34b655…2a6f
2 touches
0 conflicts
0x53699236…fede
0x34b655…2a6f
2 touches
0 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: Perpl
6 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity