← previous blocknext block →recent activity
Analyzing
Block #86,805,703
17 transactions · 13 stateful · 2026-07-10 08:48:48 UTC
Parallelism
82/100
Blocked
38%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,805,703 · 17 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
1w04w05w16w27w19w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8060f612…9559
0x34b655…2a6f
6 touches
3 conflicts
0x01df0928…3427
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0b320394…cc69
0x34b655…2a6f
4 touches
1 conflict
0x1bd2cefa…c040
0x34b655…2a6f
4 touches
1 conflict
0x1d7ead92…e6fc
0x34b655…2a6f
4 touches
1 conflict
0x47d9d6b5…e582
0x34b655…2a6f
4 touches
1 conflict
0x48203298…65cb
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 0x8060f612b1…089559
Audit this contract →
← previous block·next block →recent activity