← previous blocknext block →recent activity

Analyzing

Block #75,732,663

22 transactions · 11 stateful · 2026-05-20 01:48:18 UTC

Parallelism

86/100

Blocked

27%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,732,663  ·  22 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

0xcd54e0c4…b627

0xd32edf…ff58

5 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x147be082…7779

0x065c9d…c394

2 touches
0 conflicts

0xc45886a2…4fa6

0x065c9d…c394

2 touches
0 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

2 touches
0 conflicts

0x264c6e4e…cbb6

0x3bd359…433a

2 touches
0 conflicts

0xf6cc7de8…0b4a

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

3 conflicts on slot 0xcd54e0c403…71b627

← previous block·next block →recent activity