← previous blocknext block →recent activity
Analyzing
Block #87,714,349
29 transactions · 28 stateful · 2026-07-14 14:05:10 UTC
Parallelism
66/100
Blocked
68%
Avg conflicts / tx
2.07
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #87,714,349 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w07w110w011w112w213w314w415w516w618w519w620w722w125w626w728w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xa6389d47…9a28
0x34b655…2a6f
12 touches
15 conflicts
0x9243d2e7…9c5d
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x98834cc0…6c23
0x34b655…2a6f
6 touches
3 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
6 touches
3 conflicts
0xa64400d8…2df0
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity