← previous blocknext block →recent activity

Analyzing

Block #73,654,155

13 transactions · 12 stateful · 2026-05-10 10:19:10 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,654,155  ·  13 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

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0x6fbf2195…8660

0x34b655…2a6f

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x165e13b3…0497

0x065c9d…c394

3 touches
1 conflict

0xc123d3ef…084f

0xd32edf…ff58

3 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

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 0xf2438038b6…475fa7

← previous block·next block →recent activity