← previous blocknext block →recent activity

Analyzing

Block #75,196,620

30 transactions · 25 stateful · 2026-05-17 14:00:47 UTC

Parallelism

80/100

Blocked

56%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,196,620  ·  30 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xea57afd0…4232

0x34b655…2a6f

8 touches
6 conflicts

0x9c83a7b1…e305

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0xd8048fd7…1434

0xd32edf…ff58

5 touches
3 conflicts

0xfb6e81f1…ed2c

0x065c9d…c394

4 touches
2 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: 0x34b6552d…112a6f

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity