← previous blocknext block →recent activity

Analyzing

Block #89,749,084

19 transactions · 18 stateful · 2026-07-23 22:22:05 UTC

Parallelism

63/100

Blocked

50%

Avg conflicts / tx

0.74

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,749,084  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x3d2f528f…07f9

0x34b655…2a6f

4 touches
1 conflict

0x53142478…5458

0x34b655…2a6f

4 touches
1 conflict

0x5f56ffe5…09c0

0x34b655…2a6f

4 touches
1 conflict

0x749a4cb2…15f8

0x34b655…2a6f

4 touches
1 conflict

0x777ad666…1a52

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

← previous block·next block →recent activity