← previous blocknext block →recent activity
Analyzing
Block #87,716,263
51 transactions · 34 stateful · 2026-07-14 14:18:02 UTC
Parallelism
63/100
Blocked
71%
Avg conflicts / tx
2.9
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,716,263 · 51 txs across 19 waves · depth 19
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
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w29w310w414w023w025w126w227w328w429w530w631w740w1442w448w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
28 touches
91 conflicts
0x8b818135…eff8
0x34b655…2a6f
16 touches
28 conflicts
0xab5ba139…ea6f
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x2dfde2ed…8801
0x34b655…2a6f
10 touches
10 conflicts
0x67905f6e…02a1
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xd8675136…9a01
0x34b655…2a6f
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
91 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity