← previous blocknext block →recent activity

Analyzing

Block #75,103,136

27 transactions · 24 stateful · 2026-05-17 03:36:38 UTC

Parallelism

78/100

Blocked

58%

Avg conflicts / tx

1.3

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,103,136  ·  27 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

0x631b4113…baa9

0x34b655…2a6f

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x9a555477…19a8

0x754704…b603

6 touches
3 conflicts

0x6d0c65d9…c36f

0x34b655…2a6f

6 touches
3 conflicts

0xca0fef1c…b548

0x34b655…2a6f

6 touches
3 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 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