← previous blocknext block →recent activity
Analyzing
Block #86,921,387
7 transactions · 6 stateful · 2026-07-10 21:42:20 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,921,387 · 7 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd6b33e…9557
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x2bfb71b5…3a04
0x34b655…2a6f
2 touches
0 conflicts
0x2bfb71b5…3a05
0x34b655…2a6f
2 touches
0 conflicts
0x301e1c77…9e30
0x34b655…2a6f
2 touches
0 conflicts
0x369a943e…aef6
0x34b655…2a6f
2 touches
0 conflicts
0x378da71b…ef37
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 0x6bd6b33ee8…919557
Audit this contract →
← previous block·next block →recent activity