← previous blocknext block →recent activity

Analyzing

Block #75,301,393

18 transactions · 15 stateful · 2026-05-18 01:41:24 UTC

Parallelism

83/100

Blocked

13%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,301,393  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe8f5e33f…719c

0x34b655…2a6f

4 touches
1 conflict

0x5fad6fee…7714

0x34b655…2a6f

4 touches
1 conflict

0xa6464996…3af9

0x34b655…2a6f

4 touches
1 conflict

0xb77c59ad…4c74

0x34b655…2a6f

4 touches
1 conflict

0xde1a0ee7…c75b

0x34b655…2a6f

4 touches
1 conflict

0x7b43f938…3650

0x000000…012a

2 touches
0 conflicts

0x4dd1db39…a994

0x188d58…ea8e

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity