← previous blocknext block →recent activity

Analyzing

Block #74,458,438

18 transactions · 16 stateful · 2026-05-14 03:47:43 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,458,438  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0xc0f25d9d…67d1

0x34b655…2a6f

8 touches
6 conflicts

0xc38a1e34…37c3

0x34b655…2a6f

8 touches
6 conflicts

0xff5c097d…680c

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x2f68ee74…bf7f

0x34b655…2a6f

6 touches
3 conflicts

0x849f3e33…c095

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity