← previous blocknext block →recent activity
Analyzing
Block #86,921,482
15 transactions · 13 stateful · 2026-07-10 21:42:58 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,921,482 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w17w28w39w410w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd6b33e…9557
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7012fd2e…ae67
0x34b655…2a6f
6 touches
3 conflicts
0x1ba5d36c…9336
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
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
10 conflicts on slot 0x6bd6b33ee8…919557
Audit this contract →
← previous block·next block →recent activity