← previous blocknext block →recent activity

Analyzing

Block #75,937,609

19 transactions · 17 stateful · 2026-05-21 00:34:21 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,937,609  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 conflicts

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x2a3a1679…b3ef

0x34b655…2a6f

4 touches
1 conflict

0x30c10c87…22ec

0x34b655…2a6f

4 touches
1 conflict

0x4546ebad…b908

0x34b655…2a6f

4 touches
1 conflict

0x4d7ce95f…ecbd

0x34b655…2a6f

4 touches
1 conflict

0x61571888…b392

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity