← previous blocknext block →recent activity

Analyzing

Block #72,233,840

41 transactions · 30 stateful · 2026-05-03 20:36:34 UTC

Parallelism

81/100

Blocked

53%

Avg conflicts / tx

0.95

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,233,840  ·  41 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x6672826b…a18e

0x34b655…2a6f

8 touches
6 conflicts

0x736c5b69…fb3f

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

6 touches
3 conflicts

0x2484cc15…5afc

0x34b655…2a6f

6 touches
3 conflicts

0x2c59b868…59b3

0x34b655…2a6f

6 touches
3 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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity