← previous blocknext block →recent activity

Analyzing

Block #75,070,045

13 transactions · 11 stateful · 2026-05-16 23:55:38 UTC

Parallelism

54/100

Blocked

55%

Avg conflicts / tx

0.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,070,045  ·  13 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…0004

0x8d66a4…3095

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1a5

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

5 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xd25997d0…a683

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x10814d14…cdda

0x34b655…2a6f

4 touches
1 conflict

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: 0x8d66a43f…113095

6 conflicts on slot 0x0000000000…000004

← previous block·next block →recent activity