← previous blocknext block →recent activity
Analyzing
Block #87,792,689
22 transactions · 22 stateful · 2026-07-14 22:49:21 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,792,689 · 22 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
1w02w16w07w18w112w214w116w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6bb7e6c…bf35
0x34b655…2a6f
6 touches
3 conflicts
0x05e76e1b…39ec
0x34b655…2a6f
6 touches
3 conflicts
0xe589d762…b275
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4c623175…29e4
0x34b655…2a6f
4 touches
1 conflict
0x56f7a389…74fd
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 0xc6bb7e6c40…3dbf35
Audit this contract →
← previous block·next block →recent activity