← previous blocknext block →recent activity

Analyzing

Block #74,648,735

32 transactions · 25 stateful · 2026-05-15 01:02:07 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

0.78

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,648,735  ·  32 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

0x91abbcb1…4f3e

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0x80a6e76c…277f

0x34b655…2a6f

4 touches
1 conflict

0x97d5efed…1aa4

0x34b655…2a6f

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

15 conflicts on slot 0x91abbcb1ef…af4f3e

← previous block·next block →recent activity