← previous blocknext block →recent activity
Analyzing
Block #87,709,135
54 transactions · 40 stateful · 2026-07-14 13:30:14 UTC
Parallelism
72/100
Blocked
63%
Avg conflicts / tx
1.91
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,709,135 · 54 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w17w28w09w117w020w124w025w126w227w328w429w530w631w732w833w934w1035w1139w241w149w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
10 touches
10 conflicts
0x48315f67…c1a6
0x34b655…2a6f
8 touches
6 conflicts
0x767799cd…f423
0xc8689a…ee79
8 touches
6 conflicts
0x197e2da8…f1f4
0x34b655…2a6f
8 touches
6 conflicts
0x3b679ba3…b050
0x34b655…2a6f
8 touches
6 conflicts
0xc03846bb…73b3
0x34b655…2a6f
8 touches
6 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
66 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity