← previous blocknext block →recent activity
Analyzing
Block #94,306,407
18 transactions · 18 stateful · 2026-08-08 21:00:15 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,306,407 · 18 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
5w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xcee176f8…a030
0x34b655…2a6f
4 touches
1 conflict
0x2ad29b13…92e0
0x34b655…2a6f
2 touches
0 conflicts
0x2e77c6ca…f7c6
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x75f928fc…0465
0x34b655…2a6f
2 touches
0 conflicts
0xa2c9330e…e167
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 0x706c758c00…e62fdb
Audit this contract →
← previous block·next block →recent activity