← previous blocknext block →recent activity
Analyzing
Block #87,498,763
20 transactions · 17 stateful · 2026-07-13 14:02:36 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,498,763 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w19w210w211w313w416w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8dfb88f5…5592
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0xb568bd0a…0a72
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xc2f84a16…86b8
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
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 0x8dfb88f5fc…3e5592
Audit this contract →
← previous block·next block →recent activity