Block #72,099,318

← previous blocknext block →recent activity

Analyzing

Block #72,099,318

27 transactions · 21 stateful · 2026-05-03 05:36:54 UTC

Parallelism

74/100

Blocked

57%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,099,318  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xadac4a86…c2bc

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xb39d2b95…58b4

0xd32edf…ff58

7 touches
6 conflicts

0x44102a6e…2ea1

0x34b655…2a6f

6 touches
3 conflicts

0x4ac5588f…e61f

0x34b655…2a6f

6 touches
3 conflicts

0x674c1ed4…da3f

0x34b655…2a6f

6 touches
3 conflicts

0x75f928fc…0465

0x34b655…2a6f

6 touches
3 conflicts

0x904fc3c0…00ec

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

10 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity