← previous blocknext block →recent activity

Analyzing

Block #72,310,225

14 transactions · 9 stateful · 2026-05-04 05:09:06 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,310,225  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x58799a46…7030

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xda86e84b…fcd9

0x34b655…2a6f

4 touches
1 conflict

0x323c931a…a50c

0x34b655…2a6f

2 touches
0 conflicts

0x350f130e…902f

0x34b655…2a6f

2 touches
0 conflicts

0x3c843f4c…3a56

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 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: 0x681e908b…e1ae09

3 conflicts on slot 0x0d622e34f9…000000

← previous block·next block →recent activity