← previous blocknext block →recent activity

Analyzing

Block #75,684,649

9 transactions · 7 stateful · 2026-05-19 20:28:55 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,684,649  ·  9 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x59c40acf…a07f

0xd32edf…ff58

3 touches
1 conflict

0x35becbd1…e7e8

0x065c9d…c394

2 touches
0 conflicts

0x460f40ad…b1dc

0x065c9d…c394

2 touches
0 conflicts

0x4c43e9fb…5d5d

0x065c9d…c394

2 touches
0 conflicts

0x50c3cc97…78f9

0x065c9d…c394

2 touches
0 conflicts

0x6979db89…a7b0

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