← previous blocknext block →recent activity

Analyzing

Block #72,497,049

11 transactions · 10 stateful · 2026-05-05 01:53:36 UTC

Parallelism

55/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,497,049  ·  11 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xe6455d1f…1029

0x754704…b603

10 touches
10 conflicts

0x0d0b2509…074d

0x3bd359…433a

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0xda32df54…f757

0x065c9d…c394

3 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9538

0x188d58…ea8e

2 touches
0 conflicts

0xa980598e…ec52

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: 0x754704bc…afb603

10 conflicts on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity