← previous blocknext block →recent activity
Analyzing
Block #87,733,733
18 transactions · 17 stateful · 2026-07-14 16:14:57 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,733,733 · 18 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
1w03w04w15w26w37w08w19w110w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55c4598…2988
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x22e7ebfe…1293
0x34b655…2a6f
8 touches
6 conflicts
0xa38b0bde…bf1e
0x34b655…2a6f
8 touches
6 conflicts
0xac6f24e7…c98b
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x201679bc…0414
0x34b655…2a6f
7 touches
6 conflicts
0x665c2e0f…be75
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
10 conflicts on slot 0xa55c45989b…e52988
Audit this contract →
← previous block·next block →recent activity