← previous blocknext block →recent activity

Analyzing

Block #74,764,030

27 transactions · 23 stateful · 2026-05-15 13:52:00 UTC

Parallelism

70/100

Blocked

57%

Avg conflicts / tx

1.41

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,764,030  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

6 touches
3 conflicts

0x0d6cd751…e3c9

0x34b655…2a6f

6 touches
3 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

6 touches
3 conflicts

0x32ee90db…decc

0x34b655…2a6f

6 touches
3 conflicts

0x3582b315…0ce0

0x34b655…2a6f

6 touches
3 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x70b2e084…f863

0x34b655…2a6f

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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity