← previous blocknext block →recent activity

Analyzing

Block #75,103,810

13 transactions · 10 stateful · 2026-05-17 03:41:08 UTC

Parallelism

85/100

Blocked

20%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,103,810  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x031743cc…4992

0x065c9d…c394

4 touches
1 conflict

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0xf577ccbc…df9c

0x065c9d…c394

3 touches
1 conflict

0x67590daa…7e99

0x065c9d…c394

3 touches
1 conflict

0x26a96f1d…523f

0x34b655…2a6f

2 touches
0 conflicts

0x5a0a05c7…7df5

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x62d6e82b…a750

0x34b655…2a6f

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

1 conflict on slot 0x031743cc51…cb4992

← previous block·next block →recent activity