← previous blocknext block →recent activity

Analyzing

Block #73,964,679

8 transactions · 7 stateful · 2026-05-11 21:00:06 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,964,679  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7170c140…36bc

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0xc50e4c77…cc13

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xee230b20…5a0f

0x34b655…2a6f

6 touches
3 conflicts

0x2aef4269…ad47

0x34b655…2a6f

4 touches
1 conflict

0x9d652ee8…83ca

0x34b655…2a6f

4 touches
1 conflict

0x2cf96c0a…538a

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 0x7170c140c5…9a36bc

← previous block·next block →recent activity