← previous blocknext block →recent activity

Analyzing

Block #90,696,790

17 transactions · 17 stateful · 2026-07-27 06:11:33 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.24

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #90,696,790  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xbf78ee7f…e7fd

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x4d7e366b…7690

0x34b655…2a6f

4 touches
1 conflict

0x53d6f1c9…16c4

0x34b655…2a6f

4 touches
1 conflict

0x87923ecf…1f09

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

10 conflicts on slot 0xbf78ee7fb5…b5e7fd

← previous block·next block →recent activity