← previous blocknext block →recent activity
Analyzing
Block #86,921,901
15 transactions · 10 stateful · 2026-07-10 21:45:46 UTC
Parallelism
87/100
Blocked
30%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,921,901 · 15 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
1w08w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd6b33e…9557
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x7e5ea60a…c4ab
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
2 touches
0 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
2 touches
0 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
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