← previous blocknext block →recent activity

Analyzing

Block #74,644,242

24 transactions · 20 stateful · 2026-05-15 00:32:16 UTC

Parallelism

67/100

Blocked

55%

Avg conflicts / tx

1.54

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,644,242  ·  24 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0xfd784183…67bb

0x34b655…2a6f

7 touches
6 conflicts

0x874f5c70…608f

0x34b655…2a6f

6 touches
3 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

6 touches
3 conflicts

0x53b4ef2b…8a05

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

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: 0x34b6552d…112a6f

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity