← previous blocknext block →recent activity
Analyzing
Block #86,081,333
23 transactions · 20 stateful · 2026-07-07 00:07:28 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,081,333 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w09w010w111w212w017w118w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc4cb048e…7562
0x34b655…2a6f
6 touches
3 conflicts
0xddd7607e…9b4b
0x34b655…2a6f
5 touches
3 conflicts
0x05edf2cf…ac3c
0x34b655…2a6f
4 touches
1 conflict
0x0e1a4c2a…0107
0x34b655…2a6f
4 touches
1 conflict
0x1aaf4996…65ec
0x34b655…2a6f
4 touches
1 conflict
0x30fa662a…06e0
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity