← previous blocknext block →recent activity

Analyzing

Block #75,126,423

9 transactions · 8 stateful · 2026-05-17 06:12:04 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,126,423  ·  9 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

0xf06c2cf5…61bd

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdef19d99…c0a9

0x34b655…2a6f

4 touches
1 conflict

0x00bac013…a28c

0x91b81b…6d56

2 touches
0 conflicts

0x9560013d…8caf

0x91b81b…6d56

2 touches
0 conflicts

0x455b104f…3960

0xea1b8e…c5ec

2 touches
0 conflicts

0x4696f09d…8ad9

0xea1b8e…c5ec

2 touches
0 conflicts

0x535d2f17…3a0f

0xea1b8e…c5ec

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: 0x34b6552d…112a6f

1 conflict on slot 0xf06c2cf5e4…3161bd

← previous block·next block →recent activity