← previous blocknext block →recent activity

Analyzing

Block #72,097,967

14 transactions · 11 stateful · 2026-05-03 05:27:55 UTC

Parallelism

57/100

Blocked

55%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,097,967  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0d0b2509…074d

0x3bd359…433a

8 touches
6 conflicts

0xe6455d1f…1029

0x754704…b603

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x056ec025…dea0

0x065c9d…c394

3 touches
1 conflict

0xcd0d2d42…dbba

0xd32edf…ff58

3 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

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: 0x3bd359c1…15433a

6 conflicts on slot 0x0d0b2509ae…4b074d

← previous block·next block →recent activity