← previous blocknext block →recent activity

Analyzing

Block #75,755,236

11 transactions · 9 stateful · 2026-05-20 04:18:24 UTC

Parallelism

73/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,755,236  ·  11 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

0x8a35acfb…d1a6

0x8d66a4…3095

4 touches
1 conflict

0x7151b1ad…4520

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x0335ae80…8414

0x8d66a4…3095

4 touches
1 conflict

0x17cd1479…00bb

0x8d66a4…3095

4 touches
1 conflict

0x50e10826…843b

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a0

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a5

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

1 conflict on slot 0x8a35acfbc1…6bd1a6

← previous block·next block →recent activity