← previous blocknext block →recent activity

Analyzing

Block #75,340,242

12 transactions · 9 stateful · 2026-05-18 06:01:21 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,340,242  ·  12 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

6 touches
3 conflicts

0xe29981ca…b57f

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0022e0cd…15f7

0x065c9d…c394

2 touches
0 conflicts

0x1da235bf…0fed

0x065c9d…c394

2 touches
0 conflicts

0x369fbf86…a7e4

0x065c9d…c394

2 touches
0 conflicts

0x39678bb6…2c8c

0x065c9d…c394

2 touches
0 conflicts

0x82e3cbaa…ae67

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity