← previous blocknext block →recent activity

Analyzing

Block #75,479,465

12 transactions · 9 stateful · 2026-05-18 21:31:35 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,479,465  ·  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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0aa885fa…a3d1

0x2a68ba…90c5

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

3 touches
1 conflict

0x0699fcb7…44f9

0x065c9d…c394

3 touches
1 conflict

0x7052db88…5a53

0x065c9d…c394

3 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

2 touches
0 conflicts

0x9194f4a3…10b8

0x754704…b603

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity