← previous blocknext block →recent activity

Analyzing

Block #75,503,307

13 transactions · 11 stateful · 2026-05-19 00:15:11 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,503,307  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x826c0d98…b92f

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0000

0x04ddf6…7f33

2 touches
0 conflicts

0x00000000…0001

0x04ddf6…7f33

2 touches
0 conflicts

0x00000000…0003

0x04ddf6…7f33

2 touches
0 conflicts

0x0ef74796…cd18

0x0a3323…0a3c

2 touches
0 conflicts

0x0f045139…1cc4

0x0a3323…0a3c

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: 0x34b6552d…112a6f

1 conflict on slot 0x826c0d982f…e6b92f

← previous block·next block →recent activity