← previous blocknext block →recent activity

Analyzing

Block #72,233,770

49 transactions · 31 stateful · 2026-05-03 20:36:06 UTC

Parallelism

84/100

Blocked

61%

Avg conflicts / tx

1.16

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,233,770  ·  49 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

0x6a81cc55…7a13

0xd32edf…ff58

15 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x74e71984…ae90

0x2a68ba…90c5

6 touches
3 conflicts

0x0de7749d…5bef

0x34b655…2a6f

6 touches
3 conflicts

0xd025d7d7…f05a

0x3bd359…433a

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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 0x6a81cc55b4…997a13

← previous block·next block →recent activity