← previous blocknext block →recent activity
Analyzing
Block #87,694,426
16 transactions · 15 stateful · 2026-07-14 11:51:36 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,694,426 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda6ebfcf…d51e
0x34b655…2a6f
8 touches
6 conflicts
0x18cf36a6…a3a3
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
8 touches
6 conflicts
0xc264135b…ac7f
0x34b655…2a6f
8 touches
6 conflicts
0x98afad44…850d
0x34b655…2a6f
8 touches
6 conflicts
0xa7d10979…c5d8
0x34b655…2a6f
7 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x633e3fc4…8bf3
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 0xda6ebfcfe0…67d51e
Audit this contract →
← previous block·next block →recent activity