← previous blocknext block →recent activity
Analyzing
Block #87,579,363
21 transactions · 18 stateful · 2026-07-13 23:02:28 UTC
Parallelism
67/100
Blocked
39%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,579,363 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w011w212w316w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
12 touches
15 conflicts
0x5250e2f6…9390
0x34b655…2a6f
8 touches
6 conflicts
0xf4a27876…b09c
0x34b655…2a6f
8 touches
6 conflicts
0xdf0b4e17…ccd8
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa5420e1f…3788
0x34b655…2a6f
8 touches
6 conflicts
0xff1c6931…7633
0x34b655…2a6f
6 touches
3 conflicts
0x5036f376…c06a
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 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity