Block #72,288,167

← previous blocknext block →recent activity

Analyzing

Block #72,288,167

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

Parallelism

56/100

Blocked

61%

Avg conflicts / tx

2.04

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #72,288,167  ·  27 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x60f7fbaf…bd58

0x34b655…2a6f

20 touches
45 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x88915805…fbc9

0x34b655…2a6f

10 touches
10 conflicts

0x374426df…f445

0xc8689a…ee79

10 touches
10 conflicts

0xe4af4c87…9964

0x34b655…2a6f

10 touches
10 conflicts

0xfbabb02d…af07

0x34b655…2a6f

10 touches
10 conflicts

0xebf19faa…72cb

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

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

45 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity