← previous blocknext block →recent activity

Analyzing

Block #90,838,840

16 transactions · 15 stateful · 2026-07-27 18:06:16 UTC

Parallelism

69/100

Blocked

60%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #90,838,840  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x42041fec…bd86

0x754704…b603

8 touches
6 conflicts

0x733a5000…6e67

0x34b655…2a6f

4 touches
1 conflict

0x734ee320…caae

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xc335872c…4214

0x34b655…2a6f

4 touches
1 conflict

0xdc35d54e…172a

0x34b655…2a6f

4 touches
1 conflict

0x26d1c221…4d2a

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity