← previous blocknext block →recent activity
Analyzing
Block #85,724,968
11 transactions · 9 stateful · 2026-07-05 08:31:55 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,724,968 · 11 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
4w06w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7ac2c0f…f591
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xab3ba25f…ec78
0x34b655…2a6f
3 touches
1 conflict
0x403db36e…f444
0x34b655…2a6f
2 touches
0 conflicts
0x6b69b90f…068f
0x34b655…2a6f
2 touches
0 conflicts
0x7b5e41ac…98fd
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 0xc7ac2c0fe8…b5f591
Audit this contract →
← previous block·next block →recent activity