← previous blocknext block →recent activity
Analyzing
Block #86,798,628
10 transactions · 6 stateful · 2026-07-10 08:01:30 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,798,628 · 10 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x846048e8…98f6
0x34b655…2a6f
4 touches
1 conflict
0xdd81afb3…de3d
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a59
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a5a
0x34b655…2a6f
4 touches
1 conflict
0x14ad9c78…2414
0x34b655…2a6f
2 touches
0 conflicts
0x1928db9c…6ea9
0x34b655…2a6f
2 touches
0 conflicts
0x26b32305…893c
0x3bd359…433a
2 touches
0 conflicts
0x2d2bc2af…4f14
0x3bd359…433a
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 0x846048e8ac…5698f6
Audit this contract →
← previous block·next block →recent activity