← previous blocknext block →recent activity
Analyzing
Block #87,624,650
17 transactions · 15 stateful · 2026-07-14 04:05:18 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,624,650 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w18w29w010w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7afbac8f…9cad
0x34b655…2a6f
8 touches
6 conflicts
0x87bdb64a…593a
0x34b655…2a6f
6 touches
3 conflicts
0x87bdb64a…593b
0x34b655…2a6f
6 touches
3 conflicts
0x05975727…7fcf
0x34b655…2a6f
6 touches
3 conflicts
0x008accc4…1da7
0x34b655…2a6f
6 touches
3 conflicts
0xd209b98e…8018
0x34b655…2a6f
6 touches
3 conflicts
0x45cd8987…3132
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity