← previous blocknext block →recent activity

Analyzing

Block #74,291,002

10 transactions · 9 stateful · 2026-05-13 09:13:29 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,291,002  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xe17859a5…0950

0x065c9d…c394

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x04f2a40d…1ddc

0x065c9d…c394

2 touches
0 conflicts

0x35190c30…59e6

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

2 touches
0 conflicts

0xf823e97f…2ee6

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

1 conflict on slot 0xe17859a582…4b0950

← previous block·next block →recent activity