← previous blocknext block →recent activity

Analyzing

Block #89,538,781

19 transactions · 18 stateful · 2026-07-23 01:27:11 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,538,781  ·  19 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

0x73764161…2791

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xf51ec09c…b4a9

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x15ae3bf3…2507

0x34b655…2a6f

4 touches
1 conflict

0xcd5c0ecb…4b5f

0x34b655…2a6f

4 touches
1 conflict

0x5726a652…db2e

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 0x7376416107…df2791

← previous block·next block →recent activity