← previous blocknext block →recent activity
Analyzing
Block #86,851,165
22 transactions · 17 stateful · 2026-07-10 13:52:47 UTC
Parallelism
64/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,851,165 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w111w212w313w417w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3f93d576…f1de
0x34b655…2a6f
6 touches
3 conflicts
0xfa3848f5…98ee
0x34b655…2a6f
6 touches
3 conflicts
0x87a24499…0acf
0x34b655…2a6f
4 touches
1 conflict
0x87a24499…0ad0
0x34b655…2a6f
4 touches
1 conflict
0x88413c1a…7783
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity