← previous blocknext block →recent activity

Analyzing

Block #73,744,744

16 transactions · 14 stateful · 2026-05-10 20:30:25 UTC

Parallelism

69/100

Blocked

36%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,744,744  ·  16 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

0xedf2b5c3…9720

0xd32edf…ff58

7 touches
6 conflicts

0x7c403af1…31b1

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0004

0xd5b70d…615b

6 touches
3 conflicts

0x00000000…0000

0xd5b70d…615b

6 touches
3 conflicts

0x18aed20c…48f3

0x000000…012a

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0xe6455d1f…1029

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: 0xd32edf66…9fff58

6 conflicts on slot 0xedf2b5c3eb…f69720

← previous block·next block →recent activity