← previous blocknext block →recent activity

Analyzing

Block #75,096,468

11 transactions · 8 stateful · 2026-05-17 02:52:09 UTC

Parallelism

82/100

Blocked

13%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,096,468  ·  11 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

0x66318d5c…6fa4

0x065c9d…c394

3 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x3463c2c2…b6f9

0x34b655…2a6f

2 touches
0 conflicts

0x3492a206…c5c6

0x34b655…2a6f

2 touches
0 conflicts

0x4118bd12…924a

0x34b655…2a6f

2 touches
0 conflicts

0x4c9f8814…59f6

0x34b655…2a6f

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 0x66318d5c82…246fa4

← previous block·next block →recent activity