← previous blocknext block →recent activity
Analyzing
Block #87,709,333
44 transactions · 37 stateful · 2026-07-14 13:31:34 UTC
Parallelism
52/100
Blocked
70%
Avg conflicts / tx
4.25
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #87,709,333 · 44 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w38w415w016w117w218w319w420w521w622w723w824w936w437w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
34 touches
136 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
14 touches
21 conflicts
0x0dd44476…ef40
0x34b655…2a6f
14 touches
21 conflicts
0x767799cd…f423
0xc8689a…ee79
12 touches
15 conflicts
0xc5f2ff26…229a
0x34b655…2a6f
12 touches
15 conflicts
0x48315f67…c1a6
0x34b655…2a6f
12 touches
15 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
12 touches
15 conflicts
0x030bd256…c5c3
0x34b655…2a6f
12 touches
15 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
136 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity