← previous blocknext block →recent activity
Analyzing
Block #94,225,131
11 transactions · 9 stateful · 2026-08-08 14:08:20 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,225,131 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x713ba679…f953
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xdd0f9852…647b
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
2 touches
0 conflicts
0x1d0a04dd…b892
0x34b655…2a6f
2 touches
0 conflicts
0x1f90c45d…89c3
0x34b655…2a6f
2 touches
0 conflicts
0x278c4ae5…1639
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
1 conflict on slot 0x713ba679e5…8ff953
Audit this contract →
← previous block·next block →recent activity