← previous blocknext block →recent activity
Analyzing
Block #87,518,009
18 transactions · 16 stateful · 2026-07-13 16:11:30 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,518,009 · 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
1w02w14w05w16w28w09w311w412w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c145401…09fd
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x69ce640b…884a
0x34b655…2a6f
4 touches
1 conflict
0x85c84f98…06d7
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
6 conflicts on slot 0x2c14540166…b709fd
Audit this contract →
← previous block·next block →recent activity