← previous blocknext block →recent activity

Analyzing

Block #74,033,024

10 transactions · 8 stateful · 2026-05-12 04:37:24 UTC

Parallelism

60/100

Blocked

38%

Avg conflicts / tx

0.8

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,033,024  ·  10 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x4b214fb0…64ec

0x065c9d…c394

2 touches
0 conflicts

0x6a48363e…1d05

0x065c9d…c394

2 touches
0 conflicts

0x9af96ae8…6c1b

0x065c9d…c394

2 touches
0 conflicts

0xfa283695…cca4

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity