← previous blocknext block →recent activity

Analyzing

Block #74,513,841

13 transactions · 6 stateful · 2026-05-14 09:57:22 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,513,841  ·  13 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

0x5d4444e7…4b33

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x03f29561…a0dd

0x065c9d…c394

3 touches
1 conflict

0x7d394eaf…cfa4

0x065c9d…c394

2 touches
0 conflicts

0xc89e93ca…b7df

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x438cf5f6…f077

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: 0x065c9d28…a9c394

1 conflict on slot 0x5d4444e762…234b33

← previous block·next block →recent activity