← previous blocknext block →recent activity

Analyzing

Block #75,478,961

28 transactions · 21 stateful · 2026-05-18 21:28:04 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.79

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,478,961  ·  28 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

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x46cb45de…a566

0x188d58…ea8e

8 touches
6 conflicts

0x846f2172…fd54

0x0555e3…2b9c

8 touches
6 conflicts

0x00000000…0000

0xbad186…74ab

8 touches
6 conflicts

0x00000000…0004

0xbad186…74ab

8 touches
6 conflicts

0x8edd456e…c7e3

0x0555e3…2b9c

8 touches
6 conflicts

0x9e25d1f0…0153

0xee8c0e…1242

8 touches
6 conflicts

0x56a919c4…ab49

0xee8c0e…1242

8 touches
6 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: 0x754704bc…afb603

10 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity