← previous blocknext block →recent activity
Analyzing
Block #87,735,366
21 transactions · 19 stateful · 2026-07-14 16:25:52 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,735,366 · 21 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
1w03w17w08w19w211w012w114w215w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x767799cd…f423
0xc8689a…ee79
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf17589f…048c
0x34b655…2a6f
4 touches
1 conflict
0xda457fb4…84a6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6ed7783a…f404
0x851145…3f07
4 touches
1 conflict
0x909def91…71d2
0x851145…3f07
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity