← previous blocknext block →recent activity

Analyzing

Block #74,734,968

40 transactions · 35 stateful · 2026-05-15 10:37:43 UTC

Parallelism

82/100

Blocked

49%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,734,968  ·  40 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0xab3526…fa38

14 touches
21 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x9fc6ea79…e2dc

0x34b655…2a6f

8 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

8 touches
6 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xe69987ad…1ef5

0xd32edf…ff58

7 touches
6 conflicts

0xab945912…015e

0x34b655…2a6f

6 touches
3 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: 0xab35264b…1cfa38

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity