← previous blocknext block →recent activity

Analyzing

Block #75,132,357

17 transactions · 14 stateful · 2026-05-17 06:51:39 UTC

Parallelism

47/100

Blocked

57%

Avg conflicts / tx

2.12

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #75,132,357  ·  17 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

0x00000000…001a

0x2d84d7…d457

18 touches
36 conflicts

0x00000000…0022

0x2d84d7…d457

18 touches
36 conflicts

0x12309510…0ac2

0x000000…012a

18 touches
36 conflicts

0x98c18a60…752f

0x000000…012a

18 touches
36 conflicts

0x099b88c6…2a8a

0x4917a5…1fe8

18 touches
36 conflicts

0x4dd1db39…a994

0x188d58…ea8e

18 touches
36 conflicts

0x4dd1db39…a995

0x188d58…ea8e

18 touches
36 conflicts

0x00000000…0002

0x2d84d7…d457

18 touches
36 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: 0x2d84d79c…add457

36 conflicts on slot 0x0000000000…00001a

← previous block·next block →recent activity