← previous blocknext block →recent activity

Analyzing

Block #74,428,532

30 transactions · 22 stateful · 2026-05-14 00:28:32 UTC

Parallelism

77/100

Blocked

32%

Avg conflicts / tx

0.77

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,428,532  ·  30 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

0xb521dcfa…1a61

0xd32edf…ff58

13 touches
21 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x479ce48c…fa16

0x1b6862…e19c

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x00000000…0015

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

21 conflicts on slot 0xb521dcfa12…f71a61

← previous block·next block →recent activity