← previous blocknext block →recent activity

Analyzing

Block #74,241,454

18 transactions · 16 stateful · 2026-05-13 03:44:01 UTC

Parallelism

67/100

Blocked

56%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,241,454  ·  18 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x2a354a63…0515

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0022

0x942644…91ab

4 touches
1 conflict

0x5699efbc…bd20

0x065c9d…c394

4 touches
1 conflict

0x88018de0…f660

0x065c9d…c394

4 touches
1 conflict

0x8e66da19…66b6

0x065c9d…c394

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity