← previous blocknext block →recent activity

Analyzing

Block #75,096,062

15 transactions · 14 stateful · 2026-05-17 02:49:25 UTC

Parallelism

40/100

Blocked

64%

Avg conflicts / tx

1.93

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,096,062  ·  15 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

14 touches
21 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

10 touches
10 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x89f9fa42…7eb3

0x34b655…2a6f

6 touches
3 conflicts

0xd6aabe89…92f5

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0x97ddf780…f724

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity