← previous blocknext block →recent activity

Analyzing

Block #75,072,234

9 transactions · 9 stateful · 2026-05-17 00:10:17 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,072,234  ·  9 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

0x00000000…0004

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xa94cf3f4…554c

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

5 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

4 touches
1 conflict

0xeb0915f1…c150

0x34b655…2a6f

4 touches
1 conflict

0x0335ae80…8414

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a1

0x8d66a4…3095

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

3 conflicts on slot 0x0000000000…000004

← previous block·next block →recent activity