← previous blocknext block →recent activity

Analyzing

Block #75,003,461

8 transactions · 7 stateful · 2026-05-16 16:31:47 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,003,461  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x6e371ab2…fde7

0x541997…f5a0

8 touches
6 conflicts

0x6e371ab2…fde8

0x541997…f5a0

8 touches
6 conflicts

0x441e91e5…35cb

0x541997…f5a0

7 touches
6 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0xdbadf6b0…43b2

0x33176b…e078

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

2 touches
0 conflicts

0x0fc41e7b…6831

0x98dc6e…8633

2 touches
0 conflicts

0x5b571ba0…f13a

0x98dc6e…8633

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: 0x541997e9…30f5a0

6 conflicts on slot 0x6e371ab298…c2fde7

← previous block·next block →recent activity