← previous blocknext block →recent activity
Analyzing
Block #85,603,347
8 transactions · 7 stateful · 2026-07-04 19:00:42 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,603,347 · 8 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ea53c99…0c3e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0xe87fb2d3…fc07
0x34b655…2a6f
4 touches
1 conflict
0x1b57aac4…41a2
0x065c9d…c394
2 touches
0 conflicts
0x2e5e35d3…23a5
0x065c9d…c394
2 touches
0 conflicts
0x3447933e…6368
0x065c9d…c394
2 touches
0 conflicts
0x489d031a…407d
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
1 conflict on slot 0x7ea53c99a0…eb0c3e
Audit this contract →
← previous block·next block →recent activity