← previous blocknext block →recent activity
Analyzing
Block #87,575,882
45 transactions · 37 stateful · 2026-07-13 22:39:10 UTC
Parallelism
64/100
Blocked
73%
Avg conflicts / tx
2.73
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,575,882 · 45 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
1w02w13w14w26w07w18w29w310w419w221w522w629w330w1031w1134w1235w1336w1439w342w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xc36fa358…24cb
0x34b655…2a6f
14 touches
21 conflicts
0x8252706a…7ca5
0x34b655…2a6f
12 touches
15 conflicts
0x54b193ad…c830
0x34b655…2a6f
12 touches
15 conflicts
0x68d9d4e4…91b6
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity