← previous blocknext block →recent activity

Analyzing

Block #74,510,949

44 transactions · 28 stateful · 2026-05-14 09:37:53 UTC

Parallelism

80/100

Blocked

50%

Avg conflicts / tx

0.77

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,510,949  ·  44 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x78067279…d187

0x34b655…2a6f

6 touches
3 conflicts

0x09a4615e…b7ad

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0x3293a887…4402

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity