← previous blocknext block →recent activity
Analyzing
Block #87,718,069
17 transactions · 17 stateful · 2026-07-14 14:30:11 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,718,069 · 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
4w05w110w113w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f234b05…db39
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0x96b8889e…9eac
0x34b655…2a6f
4 touches
1 conflict
0xf37c63b8…6da2
0x34b655…2a6f
4 touches
1 conflict
0xfa3848f5…98ee
0x34b655…2a6f
4 touches
1 conflict
0x87f7db3b…33dc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x5f234b05a2…82db39
Audit this contract →
← previous block·next block →recent activity