← previous blocknext block →recent activity
Analyzing
Block #87,750,714
33 transactions · 27 stateful · 2026-07-14 18:08:33 UTC
Parallelism
85/100
Blocked
44%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,750,714 · 33 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
1w02w13w24w35w07w08w19w210w320w023w024w125w226w127w329w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2b9c6652…d14e
0x754704…b603
6 touches
3 conflicts
0x56f6adae…573c
0x34b655…2a6f
4 touches
1 conflict
0x5b8a1a43…4aea
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity