← previous blocknext block →recent activity

Analyzing

Block #75,307,361

13 transactions · 9 stateful · 2026-05-18 02:21:22 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,307,361  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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…0013

0x1b6862…e19c

4 touches
1 conflict

0xd0ec60a1…d245

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x701bbbc4…59ab

0xd32edf…ff58

3 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0x489cb750…7069

0x065c9d…c394

2 touches
0 conflicts

0x4d44eb18…d998

0x065c9d…c394

2 touches
0 conflicts

0xaa5b597d…a5ab

0x065c9d…c394

2 touches
0 conflicts

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…000013

← previous block·next block →recent activity