← previous blocknext block →recent activity
Analyzing
Block #87,593,783
22 transactions · 20 stateful · 2026-07-14 00:38:54 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,593,783 · 22 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
1w02w03w16w27w38w09w112w113w214w215w116w320w121w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xf5adc2ae…ac32
0x34b655…2a6f
6 touches
3 conflicts
0xcfddc3ab…e671
0x34b655…2a6f
6 touches
3 conflicts
0xdf39e0b5…6504
0x34b655…2a6f
6 touches
3 conflicts
0xe2513f8c…b81d
0x34b655…2a6f
6 touches
3 conflicts
0xe3ce2780…f121
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 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity