← previous blocknext block →recent activity
Analyzing
Block #88,088,141
23 transactions · 19 stateful · 2026-07-16 07:45:27 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,088,141 · 23 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
1w05w16w07w08w113w214w115w117w120w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe6e6f436…ddc0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xa1ff0729…0146
0xa6afd3…d132
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
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 0x52b477bcb8…5d7ccf
Audit this contract →
← previous block·next block →recent activity