← previous blocknext block →recent activity
Analyzing
Block #85,174,637
13 transactions · 12 stateful · 2026-07-02 19:25:30 UTC
Parallelism
77/100
Blocked
42%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,174,637 · 13 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
1w02w14w05w16w211w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x744e0a36…70f7
0x34b655…2a6f
6 touches
3 conflicts
0x086db8fc…0024
0x34b655…2a6f
4 touches
1 conflict
0x0a880509…16ca
0x34b655…2a6f
4 touches
1 conflict
0x10f8b85f…60ee
0x34b655…2a6f
4 touches
1 conflict
0x19df8d7c…4259
0x34b655…2a6f
4 touches
1 conflict
0x226feee2…63ef
0x34b655…2a6f
4 touches
1 conflict
0x51a914cf…a822
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity