← previous blocknext block →recent activity
Analyzing
Block #86,947,993
13 transactions · 11 stateful · 2026-07-11 00:40:06 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,947,993 · 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
2w05w06w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf34ae1c…04db
0x34b655…2a6f
6 touches
3 conflicts
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xac388ba5…a800
0x34b655…2a6f
4 touches
1 conflict
0xb06917e8…6985
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xaf34ae1c36…6004db
Audit this contract →
← previous block·next block →recent activity