← previous blocknext block →recent activity
Analyzing
Block #87,490,310
17 transactions · 15 stateful · 2026-07-13 13:06:02 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,490,310 · 17 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
1w02w13w04w05w16w17w28w39w411w412w413w516w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x19caa5cc…17c7
0x34b655…2a6f
6 touches
3 conflicts
0x253bf197…1e1a
0x34b655…2a6f
6 touches
3 conflicts
0x2c145401…09fd
0x34b655…2a6f
6 touches
3 conflicts
0x34731dbd…e467
0x34b655…2a6f
6 touches
3 conflicts
0x42aad825…b067
0x34b655…2a6f
6 touches
3 conflicts
0x4dc6cd61…f674
0x34b655…2a6f
6 touches
3 conflicts
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity