← previous blocknext block →recent activity
Analyzing
Block #94,760,988
18 transactions · 16 stateful · 2026-08-10 11:16:46 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,760,988 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w012w113w214w315w417w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46822f8c…d048
0x34b655…2a6f
6 touches
3 conflicts
0x4a3eff8a…16c3
0x34b655…2a6f
6 touches
3 conflicts
0x4e9b892b…6877
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xd8717dcc…b019
0x34b655…2a6f
4 touches
1 conflict
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 0x46822f8ccb…c1d048
Audit this contract →
← previous block·next block →recent activity