← previous blocknext block →recent activity

Analyzing

Block #73,653,592

16 transactions · 13 stateful · 2026-05-10 10:15:22 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x5386dc4d…0cd4

0xd32edf…ff58

5 touches
3 conflicts

0x38b5b2ce…c5bb

0xfa32f9…f3f0

4 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

0xfe3bddd2…8b48

0x3bd359…433a

4 touches
1 conflict

0x4e368b2b…09ac

0x754704…b603

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

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

3 conflicts on slot 0x5386dc4d16…cf0cd4

← previous block·next block →recent activity