← previous blocknext block →recent activity

Analyzing

Block #75,301,279

38 transactions · 33 stateful · 2026-05-18 01:40:38 UTC

Parallelism

74/100

Blocked

73%

Avg conflicts / tx

2.34

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,301,279  ·  38 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x60f7fbaf…bd58

0x34b655…2a6f

20 touches
45 conflicts

0x99a21305…dffc

0x2a68ba…90c5

12 touches
15 conflicts

0x222fc893…acc9

0xa6afd3…d132

10 touches
10 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

10 touches
10 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

10 touches
10 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

10 touches
10 conflicts

0x9394e22c…3da3

0x34b655…2a6f

10 touches
10 conflicts

0xeb0915f1…c150

0x34b655…2a6f

10 touches
10 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

45 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity