← previous blocknext block →recent activity

Analyzing

Block #73,673,706

14 transactions · 9 stateful · 2026-05-10 12:31:04 UTC

Parallelism

79/100

Blocked

22%

Avg conflicts / tx

0.14

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,673,706  ·  14 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

0x3e733ae4…4598

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x9bad8822…a28c

0x0555e3…2b9c

2 touches
0 conflicts

0xe64f78af…51a7

0x0555e3…2b9c

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a568

0x188d58…ea8e

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

1 conflict on slot 0x3e733ae4c3…f54598

← previous block·next block →recent activity