← previous blocknext block →recent activity

Analyzing

Block #90,968,171

18 transactions · 18 stateful · 2026-07-28 04:56:54 UTC

Parallelism

50/100

Blocked

56%

Avg conflicts / tx

2

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #90,968,171  ·  18 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xac2a0273…721b

0x34b655…2a6f

16 touches
28 conflicts

0xbde524f4…43bf

0x34b655…2a6f

14 touches
21 conflicts

0x81561f70…fefd

0x34b655…2a6f

14 touches
21 conflicts

0xce06a0f7…efef

0x34b655…2a6f

12 touches
15 conflicts

0x0b65d0ba…a345

0x34b655…2a6f

4 touches
1 conflict

0x1a86a19b…b4e8

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x3de796af…274f

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

28 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity