← previous blocknext block →recent activity

Analyzing

Block #73,807,117

10 transactions · 9 stateful · 2026-05-11 03:30:59 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,807,117  ·  10 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

0x5de96bd3…c60c

0x34b655…2a6f

6 touches
3 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

6 touches
3 conflicts

0xb378025c…30cf

0x34b655…2a6f

6 touches
3 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

6 touches
3 conflicts

0x5d70606a…1d53

0x34b655…2a6f

6 touches
3 conflicts

0xedb848fe…6534

0x34b655…2a6f

6 touches
3 conflicts

0x99120c08…ee84

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

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 0x5de96bd34a…ecc60c

← previous block·next block →recent activity