← previous blocknext block →recent activity

Analyzing

Block #72,495,828

13 transactions · 11 stateful · 2026-05-05 01:45:30 UTC

Parallelism

77/100

Blocked

18%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,495,828  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x5c531d4c…6776

0x065c9d…c394

5 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xb477f084…9140

0x065c9d…c394

4 touches
1 conflict

0x4664b24b…281c

0x065c9d…c394

3 touches
1 conflict

0x5a8ff700…4d99

0x065c9d…c394

3 touches
1 conflict

0x12530975…a089

0x3bd359…433a

2 touches
0 conflicts

0x4bef88e0…eaca

0x3bd359…433a

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 0x5c531d4cb0…de6776

← previous block·next block →recent activity