← previous blocknext block →recent activity

Analyzing

Block #72,288,064

44 transactions · 35 stateful · 2026-05-04 02:41:02 UTC

Parallelism

80/100

Blocked

71%

Avg conflicts / tx

1.66

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,288,064  ·  44 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x50d570b7…bbb6

0xd32edf…ff58

17 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xbe9d1d23…3de2

0x34b655…2a6f

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 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

36 conflicts on slot 0x50d570b7b4…37bbb6

← previous block·next block →recent activity