← previous blocknext block →recent activity

Analyzing

Block #88,093,231

28 transactions · 25 stateful · 2026-07-16 08:19:31 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.64

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #88,093,231  ·  28 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x9465204c…bf37

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x45e53b04…3dba

0x34b655…2a6f

6 touches
3 conflicts

0x201679bc…0414

0x34b655…2a6f

4 touches
1 conflict

0x20fbcaee…bb79

0x34b655…2a6f

4 touches
1 conflict

0x3726966a…669d

0x34b655…2a6f

4 touches
1 conflict

0x4a5956ef…e226

0x34b655…2a6f

4 touches
1 conflict

0x805d08cf…3cfc

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

10 conflicts on slot 0x9465204cd8…debf37

← previous block·next block →recent activity