← previous blocknext block →recent activity

Analyzing

Block #72,975,871

13 transactions · 9 stateful · 2026-05-07 07:03:55 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,975,871  ·  13 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

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0xe09eda07…8dda

0x2a68ba…90c5

4 touches
1 conflict

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0x5491e7ea…28e2

0x065c9d…c394

2 touches
0 conflicts

0x8f9e0823…31cd

0x065c9d…c394

2 touches
0 conflicts

0xab760535…5df2

0x065c9d…c394

2 touches
0 conflicts

0xe662fc0f…25da

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 0x0b390c6160…02dc07

← previous block·next block →recent activity