← previous blocknext block →recent activity
Analyzing
Block #87,748,957
113 transactions · 75 stateful · 2026-07-14 17:56:48 UTC
Parallelism
81/100
Blocked
75%
Avg conflicts / tx
2.74
Longest chain
22 deep
Execution timeline
did this block parallelize well?
view
block #87,748,957 · 113 txs across 22 waves · depth 22
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
wave w19
wave w20
wave w21
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w720w830w731w832w934w1036w1195w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
26 touches
78 conflicts
0x0936f5c4…579e
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…0001
0xc1ff9f…b0fc
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x9a2de05d…3e6b
0x34b655…2a6f
16 touches
28 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
14 touches
21 conflicts
0x0dd44476…ef40
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 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
78 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity