← previous blocknext block →recent activity

Analyzing

Block #73,034,229

26 transactions · 20 stateful · 2026-05-07 13:32:21 UTC

Parallelism

77/100

Blocked

45%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,034,229  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0xaa3492db…3703

0x34b655…2a6f

6 touches
3 conflicts

0xe7574014…95e2

0x34b655…2a6f

6 touches
3 conflicts

0x3702b140…97ea

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x55968d29…1d6a

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity