← previous blocknext block →recent activity

Analyzing

Block #75,549,728

12 transactions · 10 stateful · 2026-05-19 05:28:17 UTC

Parallelism

75/100

Blocked

30%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,549,728  ·  12 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

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x892daf6e…48d8

0x065c9d…c394

4 touches
1 conflict

0xb252cef0…acf9

0x065c9d…c394

2 touches
0 conflicts

0xd270d5a4…2bcf

0x065c9d…c394

2 touches
0 conflicts

0xebc1dc66…6c9d

0x065c9d…c394

2 touches
0 conflicts

0x06e40499…165e

0x1d1325…2305

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 0x5086c64a56…bb28ba

← previous block·next block →recent activity