← previous blocknext block →recent activity

Analyzing

Block #73,161,463

10 transactions · 9 stateful · 2026-05-08 03:38:40 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.6

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,161,463  ·  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

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xa7a586ac…c700

0x34b655…2a6f

4 touches
1 conflict

0x0b28bf77…e53a

0x34b655…2a6f

2 touches
0 conflicts

0x17dc7cd4…6e9d

0x34b655…2a6f

2 touches
0 conflicts

0x32ee90db…decc

0x34b655…2a6f

2 touches
0 conflicts

0x5728edaf…f1d4

0x34b655…2a6f

2 touches
0 conflicts

0x578e7f66…1b56

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 0x388e001a16…e57e04

← previous block·next block →recent activity