← previous blocknext block →recent activity
Analyzing
Block #87,489,220
21 transactions · 19 stateful · 2026-07-13 12:58:45 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,489,220 · 21 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
3w04w17w08w29w310w412w113w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af56d6…5a50
0x34b655…2a6f
12 touches
15 conflicts
0x379e8bb1…cc38
0x34b655…2a6f
10 touches
10 conflicts
0xdbc62196…3245
0x34b655…2a6f
10 touches
10 conflicts
0x3a5224d1…ee57
0x34b655…2a6f
10 touches
10 conflicts
0xb93f7106…174a
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa1002523…644f
0x34b655…2a6f
6 touches
3 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 0xe4af56d65a…785a50
Audit this contract →
← previous block·next block →recent activity