← previous blocknext block →recent activity

Analyzing

Block #75,847,896

22 transactions · 17 stateful · 2026-05-20 14:36:36 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,847,896  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a5

0x8d66a4…3095

5 touches
3 conflicts

0x00000000…0004

0x8d66a4…3095

4 touches
1 conflict

0x0335ae80…8414

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: Perpl

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity