← previous blocknext block →recent activity

Analyzing

Block #75,097,888

12 transactions · 10 stateful · 2026-05-17 03:01:39 UTC

Parallelism

75/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,097,888  ·  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

0xc389d1ff…6a00

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

2 touches
0 conflicts

0x04f20a56…dd49

0x0c65a0…0852

2 touches
0 conflicts

0x490911cc…5fea

0x0c65a0…0852

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

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 0xc389d1ff6d…226a00

← previous block·next block →recent activity