← previous blocknext block →recent activity

Analyzing

Block #89,740,750

18 transactions · 18 stateful · 2026-07-23 21:39:58 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.22

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #89,740,750  ·  18 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

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa3f095f5…bd87

0x34b655…2a6f

6 touches
3 conflicts

0x53699236…fede

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x8f63f383…6eda

0x34b655…2a6f

4 touches
1 conflict

0xa4ea096f…4510

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity