← previous blocknext block →recent activity

Analyzing

Block #75,680,181

13 transactions · 10 stateful · 2026-05-19 19:59:12 UTC

Parallelism

69/100

Blocked

30%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,680,181  ·  13 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0x2c002b08…05cf

0x065c9d…c394

3 touches
1 conflict

0xca073497…3a50

0x065c9d…c394

2 touches
0 conflicts

0xdfa159d0…1576

0x065c9d…c394

2 touches
0 conflicts

0xf65bc1dc…c99b

0x065c9d…c394

2 touches
0 conflicts

0x06e40499…165e

0x1d1325…2305

2 touches
0 conflicts

0xa17ec269…7cdd

0x1d1325…2305

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: 0x065c9d28…a9c394

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity