← previous blocknext block →recent activity
Analyzing
Block #85,545,106
11 transactions · 11 stateful · 2026-07-04 12:32:43 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,545,106 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54b193ad…c830
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x27a7dfd0…2810
0x065c9d…c394
2 touches
0 conflicts
0x2db93d48…2cc6
0x065c9d…c394
2 touches
0 conflicts
0x2fad455d…1c25
0x065c9d…c394
2 touches
0 conflicts
0x7206af11…1cef
0x065c9d…c394
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
3 conflicts on slot 0x54b193ad55…f5c830
Audit this contract →
← previous block·next block →recent activity