← previous blocknext block →recent activity

Analyzing

Block #75,512,785

13 transactions · 9 stateful · 2026-05-19 01:20:12 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,512,785  ·  13 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

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x00000000…0001

0x0fced5…b183

2 touches
0 conflicts

0x00000000…0004

0x0fced5…b183

2 touches
0 conflicts

0x00000000…0007

0x0fced5…b183

2 touches
0 conflicts

0x00000000…0009

0x0fced5…b183

2 touches
0 conflicts

0x00000000…f44c

0x0fced5…b183

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: 0x065c9d28…a9c394

1 conflict on slot 0xfcb7b8b239…6bebb3

← previous block·next block →recent activity