← previous blocknext block →recent activity
Analyzing
Block #87,879,260
29 transactions · 17 stateful · 2026-07-15 08:28:22 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,879,260 · 29 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
1w02w15w06w17w212w213w314w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80fd3987…2314
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x53537828…73fe
0x34b655…2a6f
4 touches
1 conflict
0x6a588a1b…0500
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x73dfcba5…1873
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
3 conflicts on slot 0x80fd398747…852314
Audit this contract →
← previous block·next block →recent activity