← previous blocknext block →recent activity
Analyzing
Block #87,624,744
14 transactions · 13 stateful · 2026-07-14 04:05:56 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,624,744 · 14 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
1w02w04w06w17w18w29w312w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf386bff1…b350
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x41ebf7ed…f662
0x34b655…2a6f
6 touches
3 conflicts
0x7cfe59e0…2ec1
0x34b655…2a6f
6 touches
3 conflicts
0x92e28bd4…72cc
0x34b655…2a6f
6 touches
3 conflicts
0xa84ca715…9c73
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
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 0xf386bff13e…f6b350
Audit this contract →
← previous block·next block →recent activity