← previous blocknext block →recent activity
Analyzing
Block #85,140,545
30 transactions · 27 stateful · 2026-07-02 15:38:34 UTC
Parallelism
87/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,140,545 · 30 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
2w03w07w19w010w112w115w016w120w221w022w123w026w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e2eda1…396f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x14d04bf5…6c57
0x34b655…2a6f
4 touches
1 conflict
0x23ef1567…8f31
0x34b655…2a6f
4 touches
1 conflict
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x35425b9f…9569
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
3 conflicts on slot 0x43e2eda154…aa396f
Audit this contract →
← previous block·next block →recent activity