← previous blocknext block →recent activity

Analyzing

Block #74,231,631

12 transactions · 11 stateful · 2026-05-13 02:38:41 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,231,631  ·  12 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

0xf823e97f…2ee6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x45a91e02…c331

0x065c9d…c394

3 touches
1 conflict

0x90b0df82…1e06

0xd32edf…ff58

3 touches
1 conflict

0x25fd8762…ce5d

0x065c9d…c394

2 touches
0 conflicts

0x2740f54e…1636

0x065c9d…c394

2 touches
0 conflicts

0x546a87c3…e752

0x065c9d…c394

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

3 conflicts on slot 0xf823e97fa0…262ee6

← previous block·next block →recent activity