← previous blocknext block →recent activity
Analyzing
Block #86,928,288
19 transactions · 18 stateful · 2026-07-10 22:28:28 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,928,288 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w38w09w411w513w617w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x250c8181…eef2
0x34b655…2a6f
12 touches
15 conflicts
0x5b813b1d…5968
0x34b655…2a6f
10 touches
10 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x04105a34…6eea
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0xb46ee126…a1a5
0x34b655…2a6f
8 touches
6 conflicts
0xe727ab72…768b
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x250c8181cb…57eef2
Audit this contract →
← previous block·next block →recent activity