← previous blocknext block →recent activity

Analyzing

Block #72,399,129

34 transactions · 28 stateful · 2026-05-04 15:01:25 UTC

Parallelism

71/100

Blocked

71%

Avg conflicts / tx

2.09

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #72,399,129  ·  34 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x00000000…0002

0x7e9d3a…9fda

20 touches
45 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x24968e6d…0132

0x065c9d…c394

10 touches
10 conflicts

0xbad68552…e6bf

0x34b655…2a6f

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x045819c9…d346

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

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: 0x7e9d3a8a…4f9fda

45 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity