← previous blocknext block →recent activity

Analyzing

Block #75,301,230

10 transactions · 7 stateful · 2026-05-18 01:40:18 UTC

Parallelism

70/100

Blocked

43%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,301,230  ·  10 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

0xfe3d37ee…6e67

0x34b655…2a6f

6 touches
3 conflicts

0x8d77736d…38bb

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x33018431…8f5e

0x188d58…ea8e

4 touches
1 conflict

0x6527b0cd…3c03

0x34b655…2a6f

4 touches
1 conflict

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

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: 0x34b6552d…112a6f

3 conflicts on slot 0xfe3d37ee7e…836e67

← previous block·next block →recent activity