← previous blocknext block →recent activity

Analyzing

Block #74,920,428

25 transactions · 20 stateful · 2026-05-16 07:15:38 UTC

Parallelism

72/100

Blocked

60%

Avg conflicts / tx

1.32

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,920,428  ·  25 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

0xf97ff629…b303

0xd32edf…ff58

13 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xdfa45ee2…45c6

0x34b655…2a6f

6 touches
3 conflicts

0xeb0915f1…c150

0x34b655…2a6f

6 touches
3 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

6 touches
3 conflicts

0xafd59af5…5257

0xc8689a…ee79

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: 0xd32edf66…9fff58

21 conflicts on slot 0xf97ff62996…b8b303

← previous block·next block →recent activity