← previous blocknext block →recent activity

Analyzing

Block #72,283,022

38 transactions · 31 stateful · 2026-05-04 02:07:06 UTC

Parallelism

53/100

Blocked

58%

Avg conflicts / tx

2.5

Longest chain

18 deep

Execution timeline

did this block parallelize well?

view

block #72,283,022  ·  38 txs across 18 waves  ·  depth 18
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

wave w15

wave w16

wave w17

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

22 touches
55 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x12bc0d2c…1c12

0x34b655…2a6f

10 touches
10 conflicts

0x9cc607d0…c9c7

0x34b655…2a6f

8 touches
6 conflicts

0xaa3492db…3703

0x34b655…2a6f

8 touches
6 conflicts

0xac8e97a0…8426

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

55 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity