← previous blocknext block →recent activity

Analyzing

Block #72,399,109

38 transactions · 29 stateful · 2026-05-04 15:01:17 UTC

Parallelism

82/100

Blocked

55%

Avg conflicts / tx

1.08

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,399,109  ·  38 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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

10 touches
10 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0xf0a7ca33…3c7e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xd434422b…e717

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity