← previous blocknext block →recent activity

Analyzing

Block #72,288,019

20 transactions · 14 stateful · 2026-05-04 02:40:44 UTC

Parallelism

85/100

Blocked

57%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,288,019  ·  20 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

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0x02158256…b6e3

0xd32edf…ff58

5 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x3254d19b…f714

0x34b655…2a6f

4 touches
1 conflict

0x3aa3322a…25a4

0x34b655…2a6f

4 touches
1 conflict

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: 0x34b6552d…112a6f

3 conflicts on slot 0xbb1747e217…82f78b

← previous block·next block →recent activity