← previous blocknext block →recent activity

Analyzing

Block #75,478,244

37 transactions · 15 stateful · 2026-05-18 21:23:13 UTC

Parallelism

84/100

Blocked

47%

Avg conflicts / tx

0.51

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,478,244  ·  37 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x2f9ce8a0…36c8

0xd32edf…ff58

11 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x40c0484d…8193

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x40c0484d…8192

0x188d58…ea8e

4 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x00000000…0005

0x47bae1…7568

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

15 conflicts on slot 0x2f9ce8a01d…e736c8

← previous block·next block →recent activity