← previous blocknext block →recent activity

Analyzing

Block #73,683,195

9 transactions · 7 stateful · 2026-05-10 13:35:14 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,683,195  ·  9 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

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0x2d0e0b9c…f5a9

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0003

0xab3526…fa38

4 touches
1 conflict

0xbb6daa0c…9f5f

0x522705…fcd0

4 touches
1 conflict

0x4e368b2b…09ac

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xdc7a27e1…d536

0x754704…b603

4 touches
1 conflict

0xe436ef16…99df

0x754704…b603

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xae69c12575…722379

← previous block·next block →recent activity