← previous blocknext block →recent activity
Analyzing
Block #87,703,274
24 transactions · 20 stateful · 2026-07-14 12:50:58 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,703,274 · 24 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
1w02w111w012w113w219w321w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18ec97d9…6baa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7561f24a…4522
0x34b655…2a6f
6 touches
3 conflicts
0xae8ff4a3…733f
0x34b655…2a6f
6 touches
3 conflicts
0x4fc141d9…bb37
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
6 conflicts on slot 0x18ec97d97d…d36baa
Audit this contract →
← previous block·next block →recent activity