← previous blocknext block →recent activity
Analyzing
Block #86,948,370
17 transactions · 17 stateful · 2026-07-11 00:42:38 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,948,370 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9da8da5a…aa60
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
4 touches
1 conflict
0xa412324b…90ab
0x34b655…2a6f
4 touches
1 conflict
0xa53f8fe6…3455
0x34b655…2a6f
4 touches
1 conflict
0xc9cbb059…9e23
0x34b655…2a6f
4 touches
1 conflict
0xd1db601b…c70d
0x34b655…2a6f
4 touches
1 conflict
0xfaf3835b…98c7
0x34b655…2a6f
4 touches
1 conflict
0x0335ae80…8414
0xb1dbf0…c0d3
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
3 conflicts on slot 0x9da8da5a98…f9aa60
Audit this contract →
← previous block·next block →recent activity