← previous blocknext block →recent activity

Analyzing

Block #75,096,292

16 transactions · 13 stateful · 2026-05-17 02:50:59 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,096,292  ·  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

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0xb9868b52…c77f

0x34b655…2a6f

4 touches
1 conflict

0xe5cf4194…cf9a

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0x729c91b8…9539

0x188d58…ea8e

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: 0xee8c0e9f…481242

1 conflict on slot 0x56a919c43e…27ab49

← previous block·next block →recent activity