← previous blocknext block →recent activity
Analyzing
Block #87,755,672
30 transactions · 24 stateful · 2026-07-14 18:41:42 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,755,672 · 30 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
1w04w05w06w17w18w29w310w412w514w319w420w121w527w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xb96a99db…95aa
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
8 touches
6 conflicts
0xcb76b2ed…89a5
0x34b655…2a6f
6 touches
3 conflicts
0xbd6e61f7…3ede
0x34b655…2a6f
6 touches
3 conflicts
0x819b5176…86cf
0x34b655…2a6f
6 touches
3 conflicts
0xb7dd6ebe…d725
0x34b655…2a6f
6 touches
3 conflicts
0x671886b7…46fe
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity