← previous blocknext block →recent activity
Analyzing
Block #87,120,808
19 transactions · 19 stateful · 2026-07-11 19:54:36 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,120,808 · 19 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
3w06w17w28w39w412w413w515w516w617w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d43cc69…6f83
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x861e5aef…d32c
0x34b655…2a6f
6 touches
3 conflicts
0xa0237ed3…2622
0x34b655…2a6f
6 touches
3 conflicts
0xab98deda…aec3
0x34b655…2a6f
6 touches
3 conflicts
0xab98deda…aec4
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
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
6 conflicts on slot 0x0d43cc69f6…c46f83
Audit this contract →
← previous block·next block →recent activity