← previous blocknext block →recent activity

Analyzing

Block #75,233,110

10 transactions · 8 stateful · 2026-05-17 18:04:29 UTC

Parallelism

80/100

Blocked

38%

Avg conflicts / tx

0.3

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,233,110  ·  10 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

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xfad4f7ce…4c80

0xd32edf…ff58

3 touches
1 conflict

0x4c592318…d0c9

0x065c9d…c394

2 touches
0 conflicts

0xfbad2c6c…0d32

0x188d58…ea8e

2 touches
0 conflicts

0xfbad2c6c…0d34

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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: 0x754704bc…afb603

1 conflict on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity