← previous blocknext block →recent activity

Analyzing

Block #73,815,300

10 transactions · 9 stateful · 2026-05-11 04:25:22 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,815,300  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x955017f0…b271

0x34b655…2a6f

4 touches
1 conflict

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xb1632c2f…d991

0x0a3323…0a3c

2 touches
0 conflicts

0xdeaab6a3…ccad

0x0a3323…0a3c

2 touches
0 conflicts

0x06cdf7f0…fbe6

0x3bd359…433a

2 touches
0 conflicts

0x558f6d0c…d50f

0x3bd359…433a

2 touches
0 conflicts

0x63f5c02f…6853

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: 0x34b6552d…112a6f

1 conflict on slot 0x955017f099…95b271

← previous block·next block →recent activity