← previous blocknext block →recent activity

Analyzing

Block #72,233,050

8 transactions · 7 stateful · 2026-05-03 20:31:17 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,233,050  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc1a4c088…e828

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x3bdab090…c5bf

0x34b655…2a6f

4 touches
1 conflict

0x94710b77…a921

0x34b655…2a6f

4 touches
1 conflict

0x037849a8…fa88

0x34b655…2a6f

2 touches
0 conflicts

0x319ab432…90a4

0x34b655…2a6f

2 touches
0 conflicts

0x48ac0811…2bda

0x34b655…2a6f

2 touches
0 conflicts

0x5b981a92…5335

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0xc1a4c08897…f9e828

← previous block·next block →recent activity