← previous blocknext block →recent activity

Analyzing

Block #72,288,048

37 transactions · 27 stateful · 2026-05-04 02:40:56 UTC

Parallelism

76/100

Blocked

63%

Avg conflicts / tx

1.19

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,288,048  ·  37 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

0xac2a0273…721b

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe55ceac1…bfe0

0x34b655…2a6f

10 touches
10 conflicts

0x629e09e5…692a

0x34b655…2a6f

10 touches
10 conflicts

0x6f2e60dc…e661

0x34b655…2a6f

8 touches
6 conflicts

0x6f6fc26c…3e34

0x34b655…2a6f

8 touches
6 conflicts

0x7cb2f3fa…4836

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

15 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity