← previous blocknext block →recent activity

Analyzing

Block #75,262,110

10 transactions · 8 stateful · 2026-05-17 21:18:23 UTC

Parallelism

70/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,262,110  ·  10 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

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x037849a8…fa88

0x34b655…2a6f

2 touches
0 conflicts

0x037849a8…fa8d

0x34b655…2a6f

2 touches
0 conflicts

0x21d22421…0b7a

0x34b655…2a6f

2 touches
0 conflicts

0x6c98ebd9…ca13

0x34b655…2a6f

2 touches
0 conflicts

0xded5ec0c…f0fc

0x34b655…2a6f

2 touches
0 conflicts

0xea02471d…153a

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: 0x34b6552d…112a6f

1 conflict on slot 0x310a7246ab…012dcb

← previous block·next block →recent activity