← previous blocknext block →recent activity

Analyzing

Block #74,774,671

22 transactions · 14 stateful · 2026-05-15 15:03:19 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.27

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,774,671  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x3e49348b…9445

0x34b655…2a6f

6 touches
3 conflicts

0xd504d431…1394

0x34b655…2a6f

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x5ffc25fa…b119

0x34b655…2a6f

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x62e20208…be65

0x0555e3…2b9c

2 touches
0 conflicts

0x8e80434a…a96d

0x0555e3…2b9c

2 touches
0 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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity