← previous blocknext block →recent activity

Analyzing

Block #72,283,102

44 transactions · 27 stateful · 2026-05-04 02:07:39 UTC

Parallelism

82/100

Blocked

59%

Avg conflicts / tx

1.2

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,283,102  ·  44 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xbad68552…e6bf

0x34b655…2a6f

16 touches
28 conflicts

0xea02471d…1542

0x34b655…2a6f

14 touches
21 conflicts

0x22450040…f47a

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0018

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0028

0x1b6862…e19c

12 touches
15 conflicts

0xd6071d1d…4966

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

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 0xbad6855239…f0e6bf

← previous block·next block →recent activity