← previous blocknext block →recent activity

Analyzing

Block #75,205,142

13 transactions · 9 stateful · 2026-05-17 14:57:43 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,205,142  ·  13 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

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x044d89cc…fd52

0x065c9d…c394

2 touches
0 conflicts

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x804268b7…94b9

0x065c9d…c394

2 touches
0 conflicts

0xba38536d…2b7d

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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 0x206f43799d…55e08a

← previous block·next block →recent activity