← previous blocknext block →recent activity

Analyzing

Block #72,975,896

11 transactions · 11 stateful · 2026-05-07 07:04:05 UTC

Parallelism

82/100

Blocked

9%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,975,896  ·  11 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

0xc186d76d…121d

0xd32edf…ff58

3 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

0x2e185cd9…74d1

0x065c9d…c394

2 touches
0 conflicts

0x3ea3b5bf…852f

0x065c9d…c394

2 touches
0 conflicts

0x5855c175…a893

0x065c9d…c394

2 touches
0 conflicts

0x8e4b04b8…7ff9

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: 0xd32edf66…9fff58

1 conflict on slot 0xc186d76d8e…76121d

← previous block·next block →recent activity