← previous blocknext block →recent activity

Analyzing

Block #73,034,153

18 transactions · 11 stateful · 2026-05-07 13:31:51 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,034,153  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x69941f7e…3b1d

0x34b655…2a6f

6 touches
3 conflicts

0x5d32a251…d929

0x34b655…2a6f

4 touches
1 conflict

0x742436a7…c4d4

0x34b655…2a6f

4 touches
1 conflict

0x83f3d320…fb59

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x89999c15…fdac

0x34b655…2a6f

4 touches
1 conflict

0xa6464996…3af9

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity