← previous blocknext block →recent activity

Analyzing

Block #91,061,987

20 transactions · 20 stateful · 2026-07-28 12:49:43 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.6

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #91,061,987  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x28f324ed…9db7

0x34b655…2a6f

4 touches
1 conflict

0x2aab0897…78f7

0x34b655…2a6f

4 touches
1 conflict

0x43fd3667…094b

0x34b655…2a6f

4 touches
1 conflict

0x57682f7f…b9fb

0x34b655…2a6f

4 touches
1 conflict

0x5df7cf2b…bbe5

0x34b655…2a6f

4 touches
1 conflict

0x6e6a8155…9636

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity