← previous blocknext block →recent activity

Analyzing

Block #75,478,246

16 transactions · 9 stateful · 2026-05-18 21:23:13 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,478,246  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0xfbe161dd…757b

0x3bd359…433a

4 touches
1 conflict

0x846f2172…fd54

0x0555e3…2b9c

4 touches
1 conflict

0x09beabbc…065e

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a567

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a568

0x188d58…ea8e

2 touches
0 conflicts

0x60b24061…7c23

0x188d58…ea8e

2 touches
0 conflicts

0x60b24061…7c24

0x188d58…ea8e

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 0x46cb45de01…66a566

← previous block·next block →recent activity