← previous blocknext block →recent activity

Analyzing

Block #72,498,715

13 transactions · 11 stateful · 2026-05-05 02:04:43 UTC

Parallelism

69/100

Blocked

36%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,498,715  ·  13 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

0xb9ec7373…6d65

0x065c9d…c394

5 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x29ee075c…d127

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0003

0x059114…ac3b

2 touches
0 conflicts

0x2715508c…53a4

0x059114…ac3b

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

3 conflicts on slot 0xb9ec73730a…816d65

← previous block·next block →recent activity