← previous blocknext block →recent activity

Analyzing

Block #75,307,324

13 transactions · 10 stateful · 2026-05-18 02:21:07 UTC

Parallelism

85/100

Blocked

20%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,307,324  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0c46f1c9…cd21

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0x9d2a3b24…ee7a

0x065c9d…c394

2 touches
0 conflicts

0xb9a30d54…98ef

0x065c9d…c394

2 touches
0 conflicts

0xbb08c29b…f67f

0x065c9d…c394

2 touches
0 conflicts

0xe43d5763…b49a

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