← previous blocknext block →recent activity

Analyzing

Block #74,489,224

14 transactions · 9 stateful · 2026-05-14 07:12:31 UTC

Parallelism

86/100

Blocked

11%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,489,224  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf1e5e13e…53f3

0x34b655…2a6f

4 touches
1 conflict

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0x256918f1…c4d0

0x34b655…2a6f

4 touches
1 conflict

0x2905340c…dbc6

0x34b655…2a6f

3 touches
1 conflict

0x7b97d40a…09ed

0x34b655…2a6f

2 touches
0 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

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

1 conflict on slot 0xc824469a90…af6425

← previous block·next block →recent activity