← previous blocknext block →recent activity
Analyzing
Block #87,737,434
26 transactions · 25 stateful · 2026-07-14 16:39:42 UTC
Parallelism
85/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,737,434 · 26 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
4w06w07w18w19w010w112w013w117w218w019w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x58f65aa1…8f98
0x34b655…2a6f
6 touches
3 conflicts
0x10cab052…8d64
0x34b655…2a6f
4 touches
1 conflict
0x1a1df941…41d5
0x34b655…2a6f
4 touches
1 conflict
0x1c5d445b…7a6c
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
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 0x7e5ea60ab2…b0c4ab
Audit this contract →
← previous block·next block →recent activity