← previous blocknext block →recent activity
Analyzing
Block #86,248,645
16 transactions · 14 stateful · 2026-07-07 18:44:36 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,248,645 · 16 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
1w05w16w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac6378…36f4
0x34b655…2a6f
6 touches
3 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0xf81d0d0f…cf78
0x34b655…2a6f
4 touches
1 conflict
0x4ea6a111…6e40
0x34b655…2a6f
4 touches
1 conflict
0x792a1f85…471b
0x34b655…2a6f
4 touches
1 conflict
0x96afb941…dac2
0x34b655…2a6f
4 touches
1 conflict
0xbabe821d…939b
0x34b655…2a6f
4 touches
1 conflict
0xc9b54d67…3f60
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
3 conflicts on slot 0x0eac637818…cb36f4
Audit this contract →
← previous block·next block →recent activity