← previous blocknext block →recent activity

Analyzing

Block #90,650,176

21 transactions · 20 stateful · 2026-07-27 02:17:03 UTC

Parallelism

62/100

Blocked

55%

Avg conflicts / tx

1.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #90,650,176  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x00000000…003d

0x40c49f…2af0

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

8 touches
6 conflicts

0x26d1c221…4d2a

0x34b655…2a6f

8 touches
6 conflicts

0xa6b89ebb…a66e

0x34b655…2a6f

6 touches
3 conflicts

0xf2fc1fab…45e9

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbb322930…ace5

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: 0x40c49f17…d22af0

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity