← previous blocknext block →recent activity

Analyzing

Block #89,860,331

16 transactions · 16 stateful · 2026-07-24 07:43:19 UTC

Parallelism

88/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #89,860,331  ·  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

0x183a32c3…5ef2

0x34b655…2a6f

4 touches
1 conflict

0x2d030494…3283

0x34b655…2a6f

4 touches
1 conflict

0x30b6b911…e278

0x34b655…2a6f

4 touches
1 conflict

0x4360b49f…140d

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4a8ecf20…9c19

0x34b655…2a6f

4 touches
1 conflict

0x62030a81…91be

0x34b655…2a6f

4 touches
1 conflict

0x656e970a…9010

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 0x183a32c342…a25ef2

← previous block·next block →recent activity