← previous blocknext block →recent activity

Analyzing

Block #74,412,062

12 transactions · 11 stateful · 2026-05-13 22:38:59 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,412,062  ·  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

0x2c539d94…b63a

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x6459c3d4…b121

0x065c9d…c394

2 touches
0 conflicts

0x75a54c01…4915

0x065c9d…c394

2 touches
0 conflicts

0xcb75a7e0…558b

0x065c9d…c394

2 touches
0 conflicts

0x0872abbe…9c39

0x2a68ba…90c5

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 0x2c539d94d7…4ab63a

← previous block·next block →recent activity