← previous blocknext block →recent activity
Analyzing
Block #87,615,051
19 transactions · 18 stateful · 2026-07-14 03:01:08 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,615,051 · 19 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
2w03w16w27w310w411w515w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0804b2ba…8a77
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x3f25409b…f92b
0x34b655…2a6f
6 touches
3 conflicts
0x5f72d58f…c445
0x34b655…2a6f
4 touches
1 conflict
0x71806e15…2893
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x0804b2ba81…208a77
Audit this contract →
← previous block·next block →recent activity