← previous blocknext block →recent activity

Analyzing

Block #73,353,131

15 transactions · 13 stateful · 2026-05-09 00:54:09 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,353,131  ·  15 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x0a6f5e37…6c3c

0x34b655…2a6f

2 touches
0 conflicts

0x2847cbb8…9413

0x34b655…2a6f

2 touches
0 conflicts

0x39000195…a175

0x34b655…2a6f

2 touches
0 conflicts

0x48a081a8…f441

0x34b655…2a6f

2 touches
0 conflicts

0x5e1c23e9…4f81

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity