← previous blocknext block →recent activity
Analyzing
Block #87,751,519
19 transactions · 16 stateful · 2026-07-14 18:13:56 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,751,519 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w08w112w113w014w215w316w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e088aaa…3972
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf8c9546a…ebba
0x34b655…2a6f
4 touches
1 conflict
0x87bdb64a…593a
0x34b655…2a6f
4 touches
1 conflict
0x884dd0f3…2af0
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x6e088aaa5c…d43972
Audit this contract →
← previous block·next block →recent activity