← previous blocknext block →recent activity

Analyzing

Block #74,951,198

26 transactions · 21 stateful · 2026-05-16 10:41:27 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,951,198  ·  26 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

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x54c40e2e…ec67

0xd32edf…ff58

5 touches
3 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

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: 0x34b6552d…112a6f

3 conflicts on slot 0xb9868b5233…c6c77f

← previous block·next block →recent activity