← previous blocknext block →recent activity

Analyzing

Block #72,233,702

30 transactions · 25 stateful · 2026-05-03 20:35:39 UTC

Parallelism

70/100

Blocked

72%

Avg conflicts / tx

1.87

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,233,702  ·  30 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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x00000000…0002

0x7e9d3a…9fda

14 touches
21 conflicts

0x2ed00f98…da9f

0x34b655…2a6f

12 touches
15 conflicts

0x50c2960c…5f37

0x34b655…2a6f

12 touches
15 conflicts

0x00f245ce…1e10

0x34b655…2a6f

12 touches
15 conflicts

0x2484cc15…5afc

0x34b655…2a6f

12 touches
15 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity