← previous blocknext block →recent activity

Analyzing

Block #75,079,447

23 transactions · 18 stateful · 2026-05-17 00:58:32 UTC

Parallelism

57/100

Blocked

61%

Avg conflicts / tx

1.57

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,079,447  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x631b4113…baa9

0x34b655…2a6f

10 touches
10 conflicts

0x014b941d…ccce

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf90ba4b4…6fa0

0x34b655…2a6f

6 touches
3 conflicts

0xf8480e2a…dfee

0x1b6862…e19c

4 touches
1 conflict

0x16bd489a…3ded

0x34b655…2a6f

4 touches
1 conflict

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