← previous blocknext block →recent activity
Analyzing
Block #85,131,223
13 transactions · 11 stateful · 2026-07-02 14:36:20 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,131,223 · 13 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
1w02w16w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x644919d7…9727
0x34b655…2a6f
4 touches
1 conflict
0x7b2ff50b…8f84
0x34b655…2a6f
4 touches
1 conflict
0xe96e3c16…a9f3
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x10797f0b…439a
0x34b655…2a6f
2 touches
0 conflicts
0x1589c985…7357
0x34b655…2a6f
2 touches
0 conflicts
0x1a4ea1f9…d416
0x34b655…2a6f
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 0x2406ccf7d1…d8c1cb
Audit this contract →
← previous block·next block →recent activity