← previous blocknext block →recent activity

Analyzing

Block #72,309,563

12 transactions · 10 stateful · 2026-05-04 05:04:41 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,309,563  ·  12 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

0xe59072a2…bdca

0x065c9d…c394

4 touches
1 conflict

0x1bbf996a…7ed3

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5aa85f51…0cfa

0x065c9d…c394

3 touches
1 conflict

0x85118c21…4e8e

0x065c9d…c394

3 touches
1 conflict

0xcdddc94f…0935

0x065c9d…c394

3 touches
1 conflict

0x0175b7a6…1dba

0x8d0464…4402

2 touches
0 conflicts

0x0ef1e663…8f2a

0x8d0464…4402

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 0xe59072a25e…50bdca

← previous block·next block →recent activity