← previous blocknext block →recent activity
Analyzing
Block #86,796,006
21 transactions · 19 stateful · 2026-07-10 07:43:58 UTC
Parallelism
76/100
Blocked
26%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,796,006 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w010w111w013w214w316w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c2cdec…c059
0x34b655…2a6f
6 touches
3 conflicts
0xc788862c…c259
0x34b655…2a6f
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x00958d6e…1d09
0x34b655…2a6f
4 touches
1 conflict
0x00958d6e…1d0a
0x34b655…2a6f
4 touches
1 conflict
0x34b6e036…2161
0x34b655…2a6f
4 touches
1 conflict
0x439484d9…2f92
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x95c2cdecc9…e1c059
Audit this contract →
← previous block·next block →recent activity