← previous blocknext block →recent activity
Analyzing
Block #87,918,862
29 transactions · 24 stateful · 2026-07-15 12:53:15 UTC
Parallelism
83/100
Blocked
46%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,918,862 · 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
1w02w03w04w17w18w210w011w112w113w014w115w218w322w324w125w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x590f63c9…5df9
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x01c969a3…227b
0x34b655…2a6f
4 touches
1 conflict
0x051aa260…b0a4
0x34b655…2a6f
4 touches
1 conflict
0x0a5dbc1e…74cc
0x34b655…2a6f
4 touches
1 conflict
0x13f8c55c…3061
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity