← previous blocknext block →recent activity

Analyzing

Block #72,978,136

38 transactions · 27 stateful · 2026-05-07 07:19:01 UTC

Parallelism

79/100

Blocked

52%

Avg conflicts / tx

0.97

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,978,136  ·  38 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xfdab22b6…3844

0xd32edf…ff58

15 touches
28 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

6 touches
3 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

6 touches
3 conflicts

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x150af51d…9c42

0x34b655…2a6f

4 touches
1 conflict

0x33fb93df…3232

0x34b655…2a6f

4 touches
1 conflict

0x3c35979a…975d

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

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

28 conflicts on slot 0xfdab22b6c4…5f3844

← previous block·next block →recent activity