← previous blocknext block →recent activity

Analyzing

Block #75,139,537

14 transactions · 12 stateful · 2026-05-17 07:39:29 UTC

Parallelism

50/100

Blocked

58%

Avg conflicts / tx

1.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,139,537  ·  14 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x099b88c6…2a8a

0x4917a5…1fe8

14 touches
21 conflicts

0x00000000…001a

0x2d84d7…d457

14 touches
21 conflicts

0x00000000…0022

0x2d84d7…d457

14 touches
21 conflicts

0x7332125a…5518

0x4917a5…1fe8

14 touches
21 conflicts

0x12309510…0ac2

0x000000…012a

14 touches
21 conflicts

0x98c18a60…752f

0x000000…012a

14 touches
21 conflicts

0x4dd1db39…a994

0x188d58…ea8e

14 touches
21 conflicts

0x4dd1db39…a995

0x188d58…ea8e

14 touches
21 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: 0x4917a5ec…e81fe8

21 conflicts on slot 0x099b88c6d5…b22a8a

← previous block·next block →recent activity