← previous blocknext block →recent activity
Analyzing
Block #88,351,875
20 transactions · 17 stateful · 2026-07-17 13:10:03 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,351,875 · 20 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
2w03w04w15w06w110w212w114w315w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6396a4c4…f626
0x34b655…2a6f
6 touches
3 conflicts
0x28681974…b88f
0xa6afd3…d132
4 touches
1 conflict
0x9cea6ca2…570e
0x34b655…2a6f
4 touches
1 conflict
0xd8df242f…434f
0x34b655…2a6f
4 touches
1 conflict
0xe41e8b66…3da1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0c9eb6ea…7c39
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 0x6396a4c45b…5cf626
Audit this contract →
← previous block·next block →recent activity