← previous blocknext block →recent activity

Analyzing

Block #73,655,168

18 transactions · 14 stateful · 2026-05-10 10:26:00 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,655,168  ·  18 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

0x0eac6378…36f4

0x34b655…2a6f

6 touches
3 conflicts

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0xc875b8db…299f

0x34b655…2a6f

6 touches
3 conflicts

0xcdf15f50…8ae7

0x34b655…2a6f

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

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 0x0eac637818…cb36f4

← previous block·next block →recent activity