← previous blocknext block →recent activity
Analyzing
Block #87,749,570
16 transactions · 13 stateful · 2026-07-14 18:00:54 UTC
Parallelism
69/100
Blocked
54%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,749,570 · 16 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
1w06w08w19w210w311w112w414w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb7b28ab0…40d1
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x37907fc3…3776
0x34b655…2a6f
4 touches
1 conflict
0x55c2c22c…0474
0x34b655…2a6f
4 touches
1 conflict
0xe66a4774…f253
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity