← previous blocknext block →recent activity

Analyzing

Block #90,447,905

7 transactions · 7 stateful · 2026-07-26 09:19:30 UTC

Parallelism

57/100

Blocked

43%

Avg conflicts / tx

0.57

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #90,447,905  ·  7 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xd33a109e…bdb6

0x34b655…2a6f

4 touches
1 conflict

0xe2a6942f…e69d

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x096c7f83…68af

0x34b655…2a6f

2 touches
0 conflicts

0x0a6c31fc…f4c3

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0x92385428ad…dc6941

← previous block·next block →recent activity