← previous blocknext block →recent activity
Analyzing
Block #87,252,429
23 transactions · 20 stateful · 2026-07-12 10:35:18 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,252,429 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w010w011w112w113w215w217w318w419w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x17c44db3…8888
0xa6afd3…d132
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xb94312c7…10e3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x4da61c94…532a
0x34b655…2a6f
4 touches
1 conflict
0x50a297f1…8ec7
0x34b655…2a6f
4 touches
1 conflict
0x750ea89e…134c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity