← previous blocknext block →recent activity

Analyzing

Block #74,760,023

9 transactions · 9 stateful · 2026-05-15 13:25:13 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,760,023  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x36cd3056…b5d7

0x188d58…ea8e

4 touches
1 conflict

0x0dbf9688…c6cf

0x10aeaf…5417

4 touches
1 conflict

0x36cd3056…b5d4

0x188d58…ea8e

4 touches
1 conflict

0x36cd3056…b5d5

0x188d58…ea8e

4 touches
1 conflict

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x111f72de…b33c

0x34b655…2a6f

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 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: 0x188d586d…f9ea8e

1 conflict on slot 0x36cd3056b1…f2b5d7

← previous block·next block →recent activity