← previous blocknext block →recent activity

Analyzing

Block #72,976,352

11 transactions · 9 stateful · 2026-05-07 07:07:08 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,976,352  ·  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

0xe960d9b8…2abe

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c5

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xfc7e704d…69d5

0x065c9d…c394

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xb6d60455…e4f6

0x122c0d…e3fa

2 touches
0 conflicts

0xb6d60455…e4f7

0x122c0d…e3fa

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

6 conflicts on slot 0xe960d9b81c…aa2abe

← previous block·next block →recent activity