← previous blocknext block →recent activity
Analyzing
Block #87,708,738
39 transactions · 26 stateful · 2026-07-14 13:27:35 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,708,738 · 39 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w18w019w020w121w222w323w024w126w328w229w132w133w236w437w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0xf219f7cf…7379
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0aa42ae9…ed69
0x34b655…2a6f
4 touches
1 conflict
0x1cda18d5…31c3
0x34b655…2a6f
4 touches
1 conflict
0x220e8b65…c406
0x34b655…2a6f
4 touches
1 conflict
0x2351fc25…38e8
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
6 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity