← previous blocknext block →recent activity

Analyzing

Block #90,991,563

24 transactions · 23 stateful · 2026-07-28 06:54:39 UTC

Parallelism

71/100

Blocked

65%

Avg conflicts / tx

1.71

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,991,563  ·  24 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

0x00000000…0002

0x48cba2…b48b

12 touches
15 conflicts

0xc782ec05…5bb2

0xa6afd3…d132

12 touches
15 conflicts

0x889d5e90…929a

0x2a68ba…90c5

12 touches
15 conflicts

0xc6b1d981…1be2

0xa6afd3…d132

12 touches
15 conflicts

0x00000000…003d

0xa6afd3…d132

12 touches
15 conflicts

0x40970e69…da50

0x2b46c0…1669

10 touches
10 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

10 touches
10 conflicts

0x5778d110…d2e6

0xc8689a…ee79

10 touches
10 conflicts

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: 0x48cba278…e2b48b

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity