← previous blocknext block →recent activity

Analyzing

Block #74,034,960

12 transactions · 11 stateful · 2026-05-12 04:50:15 UTC

Parallelism

75/100

Blocked

36%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,034,960  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbd7e37a9…9eb5

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xdaca243a…f9de

0x34b655…2a6f

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x82420f4a…6a68

0x065c9d…c394

2 touches
0 conflicts

0xdc299592…65c9

0x065c9d…c394

2 touches
0 conflicts

0xe9fb3e29…e3c6

0x065c9d…c394

2 touches
0 conflicts

0xf1234a56…8834

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 0xbd7e37a9b5…859eb5

← previous block·next block →recent activity