← previous blocknext block →recent activity

Analyzing

Block #90,823,516

16 transactions · 13 stateful · 2026-07-27 16:49:11 UTC

Parallelism

56/100

Blocked

54%

Avg conflicts / tx

0.81

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,823,516  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0d488000…3831

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xddd7607e…9b4b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xde55348a…f995

0x34b655…2a6f

4 touches
1 conflict

0x08d66073…e706

0x34b655…2a6f

4 touches
1 conflict

0x1683a436…2c42

0x34b655…2a6f

4 touches
1 conflict

0x7239a7a0…e541

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 0x0d488000e2…143831

← previous block·next block →recent activity