← previous blocknext block →recent activity
Analyzing
Block #87,333,423
21 transactions · 16 stateful · 2026-07-12 19:36:55 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,333,423 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w08w111w112w118w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed4a0d72…065f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x2bfb71b5…3a05
0x34b655…2a6f
4 touches
1 conflict
0x30ab53da…3529
0x34b655…2a6f
4 touches
1 conflict
0x671703d0…94b1
0x34b655…2a6f
4 touches
1 conflict
0x72880226…1435
0x34b655…2a6f
4 touches
1 conflict
0x8765edd1…a7d5
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
3 conflicts on slot 0xed4a0d72e2…41065f
Audit this contract →
← previous block·next block →recent activity