← previous blocknext block →recent activity

Analyzing

Block #74,420,696

29 transactions · 21 stateful · 2026-05-13 23:36:20 UTC

Parallelism

72/100

Blocked

52%

Avg conflicts / tx

0.69

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,420,696  ·  29 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xee19bde5…0baf

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x78cb41e1…f2c1

0xfa32f9…f3f0

4 touches
1 conflict

0x77b3496c…234e

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

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: 0xd32edf66…9fff58

10 conflicts on slot 0xee19bde558…c70baf

← previous block·next block →recent activity