← previous blocknext block →recent activity

Analyzing

Block #72,497,098

9 transactions · 7 stateful · 2026-05-05 01:53:56 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,497,098  ·  9 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

0xca04c7ad…7612

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x4e03390f…2936

0x065c9d…c394

2 touches
0 conflicts

0x5729bf1e…6e33

0x065c9d…c394

2 touches
0 conflicts

0x5f69e397…1e39

0x065c9d…c394

2 touches
0 conflicts

0x6e0a56ee…5a2a

0x065c9d…c394

2 touches
0 conflicts

0xbec2a0c7…c347

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 0xca04c7ad2f…447612

← previous block·next block →recent activity