← previous blocknext block →recent activity

Analyzing

Block #89,545,741

20 transactions · 20 stateful · 2026-07-23 02:13:42 UTC

Parallelism

55/100

Blocked

50%

Avg conflicts / tx

1.55

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #89,545,741  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x004f611b…5f47

0x34b655…2a6f

10 touches
10 conflicts

0x69d0a300…67ef

0x34b655…2a6f

10 touches
10 conflicts

0x6e19c9a0…7d86

0x34b655…2a6f

8 touches
6 conflicts

0xad862891…5d02

0x34b655…2a6f

6 touches
3 conflicts

0x1941b441…5889

0x34b655…2a6f

6 touches
3 conflicts

0xc4c059d8…185d

0x34b655…2a6f

6 touches
3 conflicts

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

21 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity