← previous blocknext block →recent activity
Analyzing
Block #85,142,544
21 transactions · 19 stateful · 2026-07-02 15:51:54 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,142,544 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w110w113w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e2eda1…396f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x264f7d7d…8444
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x63d31af4…ef45
0x34b655…2a6f
4 touches
1 conflict
0x78067279…d187
0x34b655…2a6f
4 touches
1 conflict
0x7ae63663…9d94
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
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 0x43e2eda154…aa396f
Audit this contract →
← previous block·next block →recent activity