← previous blocknext block →recent activity

Analyzing

Block #72,365,689

9 transactions · 7 stateful · 2026-05-04 11:18:32 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x71f22d99…e4cd

0x065c9d…c394

4 touches
1 conflict

0xb915c11a…b3d3

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0ab3a853…0d61

0x065c9d…c394

3 touches
1 conflict

0x8cc74299…1151

0x065c9d…c394

3 touches
1 conflict

0x01c02931…2548

0x065c9d…c394

3 touches
1 conflict

0xa9f95a76…b782

0x065c9d…c394

3 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

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 0x71f22d99ce…62e4cd

← previous block·next block →recent activity