← previous blocknext block →recent activity

Analyzing

Block #73,389,631

8 transactions · 6 stateful · 2026-05-09 04:56:50 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,389,631  ·  8 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

0xb81d3ee7…3947

0x34b655…2a6f

6 touches
3 conflicts

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0x139669b5…87d6

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x4db8d27a…d0d1

0x34b655…2a6f

2 touches
0 conflicts

0x77ce548f…0709

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 0xb81d3ee780…143947

← previous block·next block →recent activity