← previous blocknext block →recent activity

Analyzing

Block #73,693,737

18 transactions · 12 stateful · 2026-05-10 14:46:13 UTC

Parallelism

72/100

Blocked

42%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,693,737  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xae69c125…2379

0x2a68ba…90c5

8 touches
6 conflicts

0xd4a95792…5caa

0xd32edf…ff58

7 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x78520339…3183

0x065c9d…c394

3 touches
1 conflict

0x2c1a3a23…a89a

0x065c9d…c394

3 touches
1 conflict

0x10d7325e…f0cb

0x065c9d…c394

3 touches
1 conflict

0x8be2a8b2…91f2

0x3bd359…433a

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

6 conflicts on slot 0xae69c12575…722379

← previous block·next block →recent activity