← previous blocknext block →recent activity

Analyzing

Block #75,127,123

8 transactions · 8 stateful · 2026-05-17 06:16:46 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,127,123  ·  8 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

0x1aa8c1e1…433d

0x5afd3e…7620

4 touches
1 conflict

0xd735de33…6237

0x5afd3e…7620

4 touches
1 conflict

0x01a89030…f786

0x368ee5…7ca4

2 touches
0 conflicts

0x5b571ba0…f13a

0x368ee5…7ca4

2 touches
0 conflicts

0x68faa0b9…14af

0x368ee5…7ca4

2 touches
0 conflicts

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0x7a732d9d…f14f

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

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: Liquidity Book Token (LBT)

1 conflict on slot 0x1aa8c1e109…e6433d

← previous block·next block →recent activity