← previous blocknext block →recent activity
Analyzing
Block #85,566,103
9 transactions · 9 stateful · 2026-07-04 14:52:32 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,566,103 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffb8950c…23c6
0x34b655…2a6f
4 touches
1 conflict
0x934ccf76…f69c
0x34b655…2a6f
4 touches
1 conflict
0xc400ddde…e754
0x34b655…2a6f
4 touches
1 conflict
0xcb9d8462…aa6b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0xefcdf197…96a2
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
1 conflict on slot 0xffb8950c86…f023c6
Audit this contract →
← previous block·next block →recent activity