← previous blocknext block →recent activity

Analyzing

Block #75,516,861

16 transactions · 12 stateful · 2026-05-19 01:48:02 UTC

Parallelism

81/100

Blocked

17%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,516,861  ·  16 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

0x033ddbe8…850a

0x34b655…2a6f

3 touches
1 conflict

0x59ef13ba…2741

0x34b655…2a6f

3 touches
1 conflict

0x00000000…0007

0xa7a7a5…aca7

2 touches
0 conflicts

0x064b2183…071a

0xea1b8e…c5ec

2 touches
0 conflicts

0x09744403…b936

0xea1b8e…c5ec

2 touches
0 conflicts

0x1c1a981e…f3da

0xea1b8e…c5ec

2 touches
0 conflicts

0x263ef9eb…71ab

0xea1b8e…c5ec

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