← previous blocknext block →recent activity
Analyzing
Block #87,707,761
49 transactions · 39 stateful · 2026-07-14 13:21:02 UTC
Parallelism
73/100
Blocked
67%
Avg conflicts / tx
1.86
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,707,761 · 49 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w06w19w110w015w116w219w020w121w222w323w424w525w626w727w834w238w339w440w242w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x80df1435…af82
0x34b655…2a6f
10 touches
10 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xdf15e2bf…d7a9
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x1803586e…d149
0xa6afd3…d132
10 touches
10 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity