← previous blocknext block →recent activity
Analyzing
Block #94,303,426
11 transactions · 9 stateful · 2026-08-08 20:45:08 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,303,426 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w06w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc014bcf3…3ac7
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x816f6710…5b39
0x34b655…2a6f
4 touches
1 conflict
0x232f95c2…1d16
0x34b655…2a6f
4 touches
1 conflict
0x2f233eb3…6f16
0x34b655…2a6f
4 touches
1 conflict
0xa3f095f5…bd87
0x34b655…2a6f
4 touches
1 conflict
0x29bef933…913b
0x34b655…2a6f
2 touches
0 conflicts
0x2ec739bc…4ff0
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
3 conflicts on slot 0xc014bcf38f…c73ac7
Audit this contract →
← previous block·next block →recent activity