← previous blocknext block →recent activity
Analyzing
Block #85,131,970
35 transactions · 28 stateful · 2026-07-02 14:41:20 UTC
Parallelism
89/100
Blocked
36%
Avg conflicts / tx
0.49
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,131,970 · 35 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
1w02w03w14w05w112w013w114w215w321w124w226w230w032w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x731e6d82…2883
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0x4c22021d…f8a7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x8e5cc690…b06b
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: Settlement / Helper
6 conflicts on slot 0x922c7ebd9c…1c6600
Audit this contract →
← previous block·next block →recent activity