← previous blocknext block →recent activity
Analyzing
Block #87,498,411
38 transactions · 34 stateful · 2026-07-13 14:00:15 UTC
Parallelism
58/100
Blocked
68%
Avg conflicts / tx
2.08
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,498,411 · 38 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w08w19w010w111w213w114w215w316w417w518w619w721w822w924w125w232w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x369883e3…a449
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0xe20a9313…c20a
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
21 conflicts on slot 0x369883e38e…11a449
Audit this contract →
← previous block·next block →recent activity