← previous blocknext block →recent activity

Analyzing

Block #89,573,611

13 transactions · 13 stateful · 2026-07-23 05:19:55 UTC

Parallelism

69/100

Blocked

38%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,573,611  ·  13 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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2b8d9898…d525

0x34b655…2a6f

4 touches
1 conflict

0x2bac71c3…3296

0x34b655…2a6f

4 touches
1 conflict

0x4ed6b61e…e93a

0x34b655…2a6f

4 touches
1 conflict

0x5502e1cc…3910

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity