← previous blocknext block →recent activity
Analyzing
Block #86,241,164
27 transactions · 18 stateful · 2026-07-07 17:54:32 UTC
Parallelism
89/100
Blocked
39%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,241,164 · 27 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
4w06w111w012w117w118w220w124w025w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc25f1e5…2cac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x10326aa1…38a3
0x34b655…2a6f
6 touches
3 conflicts
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x6f605341…4e28
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
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 0xcc25f1e531…5f2cac
Audit this contract →
← previous block·next block →recent activity