← previous blocknext block →recent activity

Analyzing

Block #89,854,010

20 transactions · 20 stateful · 2026-07-24 07:11:32 UTC

Parallelism

80/100

Blocked

40%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,854,010  ·  20 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb1b58b33…874f

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5bd4991d…1c41

0x34b655…2a6f

4 touches
1 conflict

0x5dd18eb2…4d66

0x34b655…2a6f

4 touches
1 conflict

0x6762cac2…3fb0

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity