← previous blocknext block →recent activity
Analyzing
Block #87,587,991
25 transactions · 23 stateful · 2026-07-14 00:00:10 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,587,991 · 25 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
5w06w17w28w311w012w113w214w416w019w122w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17cc5ec3…ae0e
0x34b655…2a6f
10 touches
10 conflicts
0x157dbfb2…4089
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xad0c7701…1d83
0x34b655…2a6f
8 touches
6 conflicts
0xc0e4d476…712c
0x34b655…2a6f
8 touches
6 conflicts
0xd2453506…54e4
0x34b655…2a6f
8 touches
6 conflicts
0xe69e44b1…4c6b
0x34b655…2a6f
8 touches
6 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 0x17cc5ec39e…57ae0e
Audit this contract →
← previous block·next block →recent activity