← previous blocknext block →recent activity

Analyzing

Block #90,276,748

31 transactions · 23 stateful · 2026-07-25 18:44:09 UTC

Parallelism

87/100

Blocked

26%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #90,276,748  ·  31 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

0x1416e2fb…e2b3

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xdf64e5e6…75e8

0x34b655…2a6f

6 touches
3 conflicts

0x0db691ab…3ee3

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8f63f383…6eda

0x34b655…2a6f

4 touches
1 conflict

0xa6b48d6e…0705

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 0x1416e2fb3c…25e2b3

← previous block·next block →recent activity