← previous blocknext block →recent activity

Analyzing

Block #72,371,265

12 transactions · 11 stateful · 2026-05-04 11:55:39 UTC

Parallelism

67/100

Blocked

27%

Avg conflicts / tx

0.42

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,371,265  ·  12 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x678ea55c…aff5

0x065c9d…c394

4 touches
1 conflict

0xef70cad2…dde3

0x065c9d…c394

4 touches
1 conflict

0xa3d0ef04…56f0

0x065c9d…c394

3 touches
1 conflict

0x60ba20b2…ed07

0x065c9d…c394

3 touches
1 conflict

0x8400cd55…ea2c

0x065c9d…c394

3 touches
1 conflict

0xadd1e9fa…b6aa

0x065c9d…c394

3 touches
1 conflict

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 0x0000000000…00003d

← previous block·next block →recent activity