← previous blocknext block →recent activity
Analyzing
Block #94,294,153
12 transactions · 9 stateful · 2026-08-08 19:58:14 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,294,153 · 12 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
2w04w05w07w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xfb657a90…637f
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0xa351b7d0…8a20
0x34b655…2a6f
4 touches
1 conflict
0x33f11ee9…312a
0x34b655…2a6f
2 touches
0 conflicts
0x3e69adfb…3b62
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 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity