← previous blocknext block →recent activity
Analyzing
Block #87,753,737
21 transactions · 19 stateful · 2026-07-14 18:28:46 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,753,737 · 21 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
3w04w16w27w311w112w313w415w519w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa279b18d…63bc
0x34b655…2a6f
10 touches
10 conflicts
0xc2cb4b4a…b088
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x648bb928…97f2
0x34b655…2a6f
8 touches
6 conflicts
0x3e8b3a49…53ee
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
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
10 conflicts on slot 0xa279b18d93…8363bc
Audit this contract →
← previous block·next block →recent activity