← previous blocknext block →recent activity
Analyzing
Block #87,587,056
13 transactions · 11 stateful · 2026-07-13 23:53:54 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,587,056 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd657b668…2f18
0x34b655…2a6f
6 touches
3 conflicts
0x0b826166…904e
0x34b655…2a6f
4 touches
1 conflict
0x1146eb10…6202
0x34b655…2a6f
4 touches
1 conflict
0x1b2c54a1…5a76
0x34b655…2a6f
4 touches
1 conflict
0x1dd9a774…4647
0x34b655…2a6f
4 touches
1 conflict
0x1f2cd70b…94be
0x34b655…2a6f
4 touches
1 conflict
0x27bfe98b…2053
0x34b655…2a6f
4 touches
1 conflict
0x344bc09a…942f
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
3 conflicts on slot 0xd657b6681f…182f18
Audit this contract →
← previous block·next block →recent activity