← previous blocknext block →recent activity

Analyzing

Block #74,772,844

24 transactions · 13 stateful · 2026-05-15 14:51:05 UTC

Parallelism

79/100

Blocked

46%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,772,844  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc5a47bc8…aefb

0xd32edf…ff58

7 touches
6 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0xc94ffbe3…7d05

0x065c9d…c394

2 touches
0 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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 0xc5a47bc8fd…f6aefb

← previous block·next block →recent activity