← previous blocknext block →recent activity

Analyzing

Block #72,286,181

9 transactions · 7 stateful · 2026-05-04 02:28:22 UTC

Parallelism

67/100

Blocked

43%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,286,181  ·  9 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

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0x292f00a4…5aa8

0x065c9d…c394

3 touches
1 conflict

0x828dbd91…76aa

0xd32edf…ff58

3 touches
1 conflict

0x17e2d2a0…359e

0x34b655…2a6f

2 touches
0 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x3254d19b…f714

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity