← previous blocknext block →recent activity
Analyzing
Block #86,225,176
25 transactions · 20 stateful · 2026-07-07 16:07:47 UTC
Parallelism
72/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,225,176 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0xda3d9c9d…a3cc
0x34b655…2a6f
5 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x68311b0c…9c3d
0x34b655…2a6f
4 touches
1 conflict
0x93bdcafa…919a
0x34b655…2a6f
4 touches
1 conflict
0x999606c2…e4ab
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity