← previous blocknext block →recent activity

Analyzing

Block #74,283,573

18 transactions · 17 stateful · 2026-05-13 08:24:00 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,283,573  ·  18 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0x9b7b3dfe…6604

0xd32edf…ff58

5 touches
3 conflicts

0xdcfdfa7a…7458

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity