← previous blocknext block →recent activity
Analyzing
Block #85,920,839
14 transactions · 11 stateful · 2026-07-06 06:16:11 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,920,839 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2e56e59…e6ff
0x34b655…2a6f
4 touches
1 conflict
0x63ce81c4…c889
0x34b655…2a6f
4 touches
1 conflict
0x1d3dac50…4731
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x1e89113a…2fe2
0x34b655…2a6f
2 touches
0 conflicts
0x2895e9ff…95e9
0x34b655…2a6f
2 touches
0 conflicts
0x28be48f5…d50b
0x34b655…2a6f
2 touches
0 conflicts
0x3d586481…5158
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 0xc2e56e59db…bfe6ff
Audit this contract →
← previous block·next block →recent activity