← previous blocknext block →recent activity

Analyzing

Block #90,205,583

21 transactions · 21 stateful · 2026-07-25 12:45:19 UTC

Parallelism

57/100

Blocked

62%

Avg conflicts / tx

1.81

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #90,205,583  ·  21 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

0xf3d10975…0d07

0x34b655…2a6f

16 touches
28 conflicts

0xea02471d…1542

0x34b655…2a6f

16 touches
28 conflicts

0xbde524f4…43bf

0x34b655…2a6f

12 touches
15 conflicts

0x4bc1abab…5874

0x34b655…2a6f

12 touches
15 conflicts

0xdd5f64d6…8a22

0x34b655…2a6f

9 touches
10 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x34a1ee7e…fb20

0x34b655…2a6f

6 touches
3 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: Perpl

28 conflicts on slot 0xf3d10975b0…050d07

← previous block·next block →recent activity