← previous blocknext block →recent activity

Analyzing

Block #72,496,365

9 transactions · 8 stateful · 2026-05-05 01:49:04 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,496,365  ·  9 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

0x0acb2c12…cb0a

0x065c9d…c394

4 touches
1 conflict

0x452c8517…3974

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2f3b95f2…2416

0x065c9d…c394

3 touches
1 conflict

0xbe64a8fd…2cc1

0x065c9d…c394

3 touches
1 conflict

0x980709df…bfd9

0x065c9d…c394

3 touches
1 conflict

0xaf502c26…a7b5

0x065c9d…c394

3 touches
1 conflict

0x3cd91bc3…061f

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 0x0acb2c120f…7bcb0a

← previous block·next block →recent activity