← previous blocknext block →recent activity
Analyzing
Block #87,704,791
24 transactions · 20 stateful · 2026-07-14 13:01:09 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,704,791 · 24 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
1w03w04w111w012w113w214w319w220w121w022w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x43fab434…896f
0xa6afd3…d132
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x67905f6e…02a1
0x34b655…2a6f
4 touches
1 conflict
0x7837c02d…0965
0x34b655…2a6f
4 touches
1 conflict
0x8fe37a3f…4c89
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