← previous blocknext block →recent activity

Analyzing

Block #75,139,404

14 transactions · 9 stateful · 2026-05-17 07:38:36 UTC

Parallelism

79/100

Blocked

22%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,139,404  ·  14 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

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xca3e49c7…af95

0x065c9d…c394

3 touches
1 conflict

0x51ca3051…0972

0x3bd359…433a

2 touches
0 conflicts

0x76f2524a…306c

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0000

0x614b85…a284

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: 0x065c9d28…a9c394

3 conflicts on slot 0xba38536db1…342b7d

← previous block·next block →recent activity