← previous blocknext block →recent activity

Analyzing

Block #75,700,600

8 transactions · 6 stateful · 2026-05-19 22:14:45 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,700,600  ·  8 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0aa885fa…a3d1

0x2a68ba…90c5

4 touches
1 conflict

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0x1df76bbd…15b0

0x065c9d…c394

3 touches
1 conflict

0x2e9a1d98…6123

0x065c9d…c394

2 touches
0 conflicts

0x5f77d607…2c84

0x065c9d…c394

2 touches
0 conflicts

0xc05efefc…9ca7

0x065c9d…c394

2 touches
0 conflicts

0xdfa159d0…1576

0x065c9d…c394

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity