← previous blocknext block →recent activity

Analyzing

Block #73,837,554

20 transactions · 17 stateful · 2026-05-11 06:53:30 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,837,554  ·  20 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

0xb81d3ee7…3947

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x31b73044…b74b

0xd32edf…ff58

5 touches
3 conflicts

0x3702b140…97ea

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x4a6debf9…6762

0x34b655…2a6f

4 touches
1 conflict

0x56253fc2…d5a1

0x34b655…2a6f

4 touches
1 conflict

0x65e795ca…0320

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

6 conflicts on slot 0xb81d3ee780…143947

← previous block·next block →recent activity