← previous blocknext block →recent activity

Analyzing

Block #76,033,969

26 transactions · 16 stateful · 2026-05-21 11:15:58 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #76,033,969  ·  26 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

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xe57b349c…eec5

0x065c9d…c394

5 touches
3 conflicts

0xd58ae1de…9aa6

0xd32edf…ff58

5 touches
3 conflicts

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xcce2fd99…a8eb

0x3bd359…433a

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: Kuru Exchange: MarginAccount

3 conflicts on slot 0xc3c8642ae9…317da5

← previous block·next block →recent activity