← previous blocknext block →recent activity

Analyzing

Block #72,233,711

8 transactions · 6 stateful · 2026-05-03 20:35:42 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,233,711  ·  8 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

0x9ba43a03…c3af

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe036c1fd…accc

0x065c9d…c394

4 touches
1 conflict

0x58de9cfb…d4c3

0x065c9d…c394

3 touches
1 conflict

0xa12a01b7…e3ba

0x065c9d…c394

3 touches
1 conflict

0x3358ddf8…8ac9

0x065c9d…c394

3 touches
1 conflict

0xd28d4f05…f4fa

0x065c9d…c394

2 touches
0 conflicts

0xf80ca3f8…f0ec

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 0x9ba43a03da…0ac3af

← previous block·next block →recent activity