← previous blocknext block →recent activity

Analyzing

Block #74,230,092

12 transactions · 9 stateful · 2026-05-13 02:28:28 UTC

Parallelism

75/100

Blocked

22%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,230,092  ·  12 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

0x768cffcd…2648

0x34b655…2a6f

6 touches
3 conflicts

0xa26c29a3…c434

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x4e9150e0…5802

0x065c9d…c394

2 touches
0 conflicts

0x6739ff0a…6fe1

0x065c9d…c394

2 touches
0 conflicts

0x76441658…e2d2

0x065c9d…c394

2 touches
0 conflicts

0xb7307664…f7b2

0x065c9d…c394

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