← previous blocknext block →recent activity

Analyzing

Block #72,221,090

12 transactions · 9 stateful · 2026-05-03 19:10:58 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,221,090  ·  12 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

0xd9ee946c…8534

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x11690adc…58c7

0x065c9d…c394

3 touches
1 conflict

0x8c918f3a…52e5

0x065c9d…c394

3 touches
1 conflict

0x20404ffc…74ec

0x065c9d…c394

2 touches
0 conflicts

0x36e52926…59cb

0x065c9d…c394

2 touches
0 conflicts

0x77a88986…e5b8

0x065c9d…c394

2 touches
0 conflicts

0xf9d262f1…5850

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 0xd9ee946ca3…ae8534

← previous block·next block →recent activity