← previous blocknext block →recent activity

Analyzing

Block #72,859,206

13 transactions · 10 stateful · 2026-05-06 18:07:26 UTC

Parallelism

69/100

Blocked

40%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,859,206  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x65668119…e8b3

0xd32edf…ff58

7 touches
6 conflicts

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x85ed7830…fcd3

0x065c9d…c394

2 touches
0 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

2 touches
0 conflicts

0xf27f3b98…de44

0x065c9d…c394

2 touches
0 conflicts

0x264c6e4e…cbb6

0x3bd359…433a

2 touches
0 conflicts

0x5d82c9b5…004c

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: 0xd32edf66…9fff58

6 conflicts on slot 0x65668119eb…9de8b3

← previous block·next block →recent activity