← previous blocknext block →recent activity

Analyzing

Block #75,516,160

24 transactions · 12 stateful · 2026-05-19 01:43:16 UTC

Parallelism

92/100

Blocked

8%

Avg conflicts / tx

0.04

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,516,160  ·  24 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

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0x172c5dcd…e2f2

0x065c9d…c394

2 touches
0 conflicts

0x24f03fab…a4fc

0x065c9d…c394

2 touches
0 conflicts

0x82e99b90…38cd

0x065c9d…c394

2 touches
0 conflicts

0x955617f4…7d1f

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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