← previous blocknext block →recent activity

Analyzing

Block #73,343,725

19 transactions · 15 stateful · 2026-05-08 23:51:29 UTC

Parallelism

74/100

Blocked

33%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,343,725  ·  19 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

0x16b57534…3328

0xd32edf…ff58

9 touches
10 conflicts

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0x036056…1881

2 touches
0 conflicts

0x3e8a4a5c…5929

0x036056…1881

2 touches
0 conflicts

0xc7949ba2…7650

0x036056…1881

2 touches
0 conflicts

0xefb186a4…a12b

0x036056…1881

2 touches
0 conflicts

0xd04ec0aa…90a2

0x065c9d…c394

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: 0xd32edf66…9fff58

10 conflicts on slot 0x16b5753436…073328

← previous block·next block →recent activity