← previous blocknext block →recent activity
Analyzing
Block #87,731,493
14 transactions · 12 stateful · 2026-07-14 15:59:58 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,731,493 · 14 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
1w02w13w25w06w17w09w210w311w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0571291…b6ca
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xcd7515c3…eb00
0xd32edf…ff58
5 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9a432c91…88e0
0x34b655…2a6f
4 touches
1 conflict
0xbf0e051a…10a0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc8536f01…eb88
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
10 conflicts on slot 0xf057129188…c2b6ca
Audit this contract →
← previous block·next block →recent activity