← previous blocknext block →recent activity

Analyzing

Block #72,036,933

38 transactions · 26 stateful · 2026-05-02 22:41:38 UTC

Parallelism

66/100

Blocked

65%

Avg conflicts / tx

2.13

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #72,036,933  ·  38 txs across 13 waves  ·  depth 13
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

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

0x1c913164…5c2e

0x34b655…2a6f

20 touches
45 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

18 touches
36 conflicts

0xb6818fd3…c885

0x34b655…2a6f

16 touches
28 conflicts

0xc6417de0…2191

0xc8689a…ee79

14 touches
21 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

14 touches
21 conflicts

0x908d4442…2c4b

0x34b655…2a6f

14 touches
21 conflicts

0x99f080dc…58c1

0x34b655…2a6f

14 touches
21 conflicts

0x9be2b99a…a959

0x34b655…2a6f

14 touches
21 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

45 conflicts on slot 0x1c913164f5…845c2e

← previous block·next block →recent activity