← previous blocknext block →recent activity

Analyzing

Block #75,478,689

30 transactions · 17 stateful · 2026-05-18 21:26:13 UTC

Parallelism

87/100

Blocked

41%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,478,689  ·  30 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x746bae2e…4384

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0004

0xca50b9…1d03

6 touches
3 conflicts

0x6320bc8e…f9a3

0xd18b7e…414b

6 touches
3 conflicts

0x00000000…0000

0xca50b9…1d03

6 touches
3 conflicts

0x8f1dbe88…8e36

0xee8c0e…1242

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0003

0x63e48b…53f2

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 0x746bae2e3c…cf4384

← previous block·next block →recent activity