← previous blocknext block →recent activity

Analyzing

Block #74,033,592

11 transactions · 10 stateful · 2026-05-12 04:41:09 UTC

Parallelism

64/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,033,592  ·  11 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

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xbf763853…0305

0xa6afd3…d132

3 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001b

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002b

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity