← previous blocknext block →recent activity

Analyzing

Block #72,571,154

20 transactions · 20 stateful · 2026-05-05 10:07:00 UTC

Parallelism

55/100

Blocked

50%

Avg conflicts / tx

1.7

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,571,154  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x81e1f4e8…08d7

0x34b655…2a6f

8 touches
6 conflicts

0x37d49489…9309

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x090637c1…37b3

0x34b655…2a6f

4 touches
1 conflict

0x17d87f0d…bfc5

0x34b655…2a6f

4 touches
1 conflict

0x3d34f2bd…5d63

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity