← previous blocknext block →recent activity
Analyzing
Block #87,065,318
17 transactions · 15 stateful · 2026-07-11 13:44:00 UTC
Parallelism
76/100
Blocked
27%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,065,318 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w19w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0xb13b96bd…a3cb
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xfaef7662…f79b
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x236b16bf…ea47
0x34b655…2a6f
4 touches
1 conflict
0x5e67eb31…015a
0x34b655…2a6f
4 touches
1 conflict
0x619c81de…01b4
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity