← previous blocknext block →recent activity

Analyzing

Block #72,496,270

10 transactions · 8 stateful · 2026-05-05 01:48:25 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,496,270  ·  10 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

0x68aaa5ab…2ee9

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe02b02f5…20e6

0x065c9d…c394

3 touches
1 conflict

0x39df3e3e…deb0

0x065c9d…c394

3 touches
1 conflict

0x02e0c10f…a495

0x065c9d…c394

2 touches
0 conflicts

0x0d57da06…62cb

0x065c9d…c394

2 touches
0 conflicts

0x55b8eb99…28fc

0x065c9d…c394

2 touches
0 conflicts

0x62360ee4…9af3

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 0x68aaa5ab3a…b12ee9

← previous block·next block →recent activity