← previous blocknext block →recent activity
Analyzing
Block #87,733,148
37 transactions · 32 stateful · 2026-07-14 16:11:03 UTC
Parallelism
62/100
Blocked
66%
Avg conflicts / tx
2.19
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,733,148 · 37 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w07w114w215w316w417w518w619w720w821w922w1026w727w828w129w930w1031w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x88f37d98…6792
0x34b655…2a6f
12 touches
15 conflicts
0xa55c4598…2988
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0x3726966a…669d
0x34b655…2a6f
8 touches
6 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
8 touches
6 conflicts
0x67905f6e…02a1
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity