← previous blocknext block →recent activity
Analyzing
Block #88,343,073
13 transactions · 13 stateful · 2026-07-17 12:11:08 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,343,073 · 13 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
1w02w05w06w17w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cc477b5…1cf3
0x34b655…2a6f
6 touches
3 conflicts
0xf9f9800f…38fa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0d2e1791…c1dd
0x34b655…2a6f
4 touches
1 conflict
0x404120f4…fbaa
0x34b655…2a6f
4 touches
1 conflict
0x427d1120…4eb1
0x34b655…2a6f
4 touches
1 conflict
0x51de484c…3fae
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b43
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 0x5cc477b5ef…3f1cf3
Audit this contract →
← previous block·next block →recent activity