← previous blocknext block →recent activity

Analyzing

Block #72,295,982

36 transactions · 31 stateful · 2026-05-04 03:34:11 UTC

Parallelism

78/100

Blocked

68%

Avg conflicts / tx

1.83

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,295,982  ·  36 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

0xb9d2cf20…a668

0x34b655…2a6f

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0x9ce014bf…d7d5

0xd32edf…ff58

11 touches
15 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

10 touches
10 conflicts

0xbbee74c2…567a

0x065c9d…c394

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x3254d19b…f714

0x34b655…2a6f

8 touches
6 conflicts

0x5af73b09…92d5

0x34b655…2a6f

8 touches
6 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 0xb9d2cf2005…28a668

← previous block·next block →recent activity