← previous blocknext block →recent activity
Analyzing
Block #87,666,714
22 transactions · 22 stateful · 2026-07-14 08:46:25 UTC
Parallelism
77/100
Blocked
32%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,666,714 · 22 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
1w02w15w06w111w012w113w214w316w420w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24f6d4ca…c33b
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x78346476…4311
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x03afadfb…d3a4
0x34b655…2a6f
6 touches
3 conflicts
0x7afbac8f…9cad
0x34b655…2a6f
6 touches
3 conflicts
0x4e1ce17e…98a7
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x24f6d4ca30…1ec33b
Audit this contract →
← previous block·next block →recent activity