← previous blocknext block →recent activity

Analyzing

Block #74,638,197

11 transactions · 9 stateful · 2026-05-14 23:51:59 UTC

Parallelism

64/100

Blocked

44%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,638,197  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x8470c491…6c57

0xd32edf…ff58

7 touches
6 conflicts

0xfbbc35e2…f66b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x1c51ee12…c757

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001f

0x1b6862…e19c

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

6 conflicts on slot 0x8470c4912d…ee6c57

← previous block·next block →recent activity