← previous blocknext block →recent activity

Analyzing

Block #75,195,681

14 transactions · 14 stateful · 2026-05-17 13:54:28 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.29

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,195,681  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xfe2bac2b…2cec

0x065c9d…c394

10 touches
10 conflicts

0xf3d7a307…4d63

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

6 touches
3 conflicts

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0x5b633c19…3279

0x065c9d…c394

5 touches
3 conflicts

0xaf159d50…2fbf

0x065c9d…c394

5 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

4 touches
1 conflict

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

10 conflicts on slot 0xfe2bac2b2f…482cec

← previous block·next block →recent activity