← previous blocknext block →recent activity
Analyzing
Block #87,048,887
14 transactions · 13 stateful · 2026-07-11 11:54:19 UTC
Parallelism
43/100
Blocked
62%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,048,887 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w58w610w711w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x75959b84…9bda
0x34b655…2a6f
10 touches
10 conflicts
0x7506443a…4820
0x34b655…2a6f
8 touches
6 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
8 touches
6 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0xc368d7fd…aaec
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity