← previous blocknext block →recent activity
Analyzing
Block #87,707,572
64 transactions · 41 stateful · 2026-07-14 13:19:46 UTC
Parallelism
88/100
Blocked
59%
Avg conflicts / tx
0.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,707,572 · 64 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
7w013w015w017w118w219w020w121w223w324w025w128w129w233w034w135w236w337w443w344w346w148w253w559w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xf6cc0644…47ec
0xd32edf…ff58
7 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity