← previous blocknext block →recent activity
Analyzing
Block #88,352,219
21 transactions · 15 stateful · 2026-07-17 13:12:21 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,352,219 · 21 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
7w08w19w210w313w014w115w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x55b4e430…44cb
0x754704…b603
4 touches
1 conflict
0x3feeb519…f970
0x0a2fbf…29b1
4 touches
1 conflict
0x3feeb519…f971
0x0a2fbf…29b1
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6396a4c4…f626
0x34b655…2a6f
4 touches
1 conflict
0x94e68337…5eb0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity