← previous blocknext block →recent activity

Analyzing

Block #74,511,034

19 transactions · 14 stateful · 2026-05-14 09:38:27 UTC

Parallelism

84/100

Blocked

43%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,511,034  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfe20cb8f…f03d

0x34b655…2a6f

6 touches
3 conflicts

0xbda819b2…76d1

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c4

0x1b6862…e19c

4 touches
1 conflict

0x0d2947c3…98d6

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity