← previous blocknext block →recent activity

Analyzing

Block #89,579,820

16 transactions · 14 stateful · 2026-07-23 06:01:20 UTC

Parallelism

88/100

Blocked

21%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,579,820  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xfaf3835b…98c7

0x34b655…2a6f

4 touches
1 conflict

0xf3343d6f…bbde

0x34b655…2a6f

4 touches
1 conflict

0xf3343d6f…bbdf

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x07f4b10c…bea6

0x34b655…2a6f

4 touches
1 conflict

0x38902419…bb3b

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x64aaadbf…f9f3

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

1 conflict on slot 0xfaf3835bd4…5298c7

← previous block·next block →recent activity