← previous blocknext block →recent activity

Analyzing

Block #89,865,113

10 transactions · 9 stateful · 2026-07-24 08:07:23 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,865,113  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x947bb79d…6458

0x34b655…2a6f

4 touches
1 conflict

0xa9e2a7fb…6218

0x34b655…2a6f

4 touches
1 conflict

0x06c2c8c1…c2a8

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x0c227c3f…d2e3

0x34b655…2a6f

3 touches
1 conflict

0x2127ebd5…7b99

0x34b655…2a6f

2 touches
0 conflicts

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

1 conflict on slot 0xc824469a90…af6425

← previous block·next block →recent activity