← previous blocknext block →recent activity

Analyzing

Block #90,993,716

20 transactions · 19 stateful · 2026-07-28 07:05:36 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,993,716  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x478e71ff…6cc6

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xb77363ff…ace7

0x34b655…2a6f

6 touches
3 conflicts

0x7e1faa73…bfbf

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x9dec86a4…0e47

0x34b655…2a6f

4 touches
1 conflict

0xbb96f8af…205f

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 0x478e71ffc9…0d6cc6

← previous block·next block →recent activity