← previous blocknext block →recent activity

Analyzing

Block #74,744,947

37 transactions · 26 stateful · 2026-05-15 11:44:11 UTC

Parallelism

78/100

Blocked

50%

Avg conflicts / tx

0.97

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,744,947  ·  37 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

0x8ee5cd14…d96a

0xd32edf…ff58

15 touches
28 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb81

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

28 conflicts on slot 0x8ee5cd144d…3ad96a

← previous block·next block →recent activity