← previous blocknext block →recent activity

Analyzing

Block #74,736,206

26 transactions · 20 stateful · 2026-05-15 10:45:55 UTC

Parallelism

77/100

Blocked

55%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,736,206  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x57005ff7…1a96

0xd32edf…ff58

9 touches
10 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0xd71ea2ea…386b

0x065c9d…c394

7 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

6 touches
3 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

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

10 conflicts on slot 0x57005ff722…2e1a96

← previous block·next block →recent activity