← previous blocknext block →recent activity

Analyzing

Block #74,461,391

20 transactions · 11 stateful · 2026-05-14 04:07:20 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,461,391  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2484cc15…5afc

0x34b655…2a6f

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x144f21e3…ba1d

0x1efe02…37d6

2 touches
0 conflicts

0x8b2d18b7…c555

0x1efe02…37d6

2 touches
0 conflicts

0x51a3625d…b7c6

0x699abc…6a3b

2 touches
0 conflicts

0x87bbe3ea…3f44

0x699abc…6a3b

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