← previous blocknext block →recent activity
Analyzing
Block #87,691,533
40 transactions · 28 stateful · 2026-07-14 11:32:16 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,691,533 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w010w011w115w018w019w121w122w024w127w228w129w330w433w234w535w637w138w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x4b80417b…75c3
0x34b655…2a6f
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x638185ad…aa16
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0000
0xb02793…e402
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity