← previous blocknext block →recent activity

Analyzing

Block #75,301,302

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

Parallelism

80/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x33018431…8f5c

0x188d58…ea8e

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0xb36c6b74…473d

0x065c9d…c394

2 touches
0 conflicts

0xcaaca573…465e

0x065c9d…c394

2 touches
0 conflicts

0xdcb86d84…a670

0x065c9d…c394

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: Perpl

1 conflict on slot 0x676f9f01ee…dea8ac

← previous block·next block →recent activity