← previous blocknext block →recent activity

Analyzing

Block #75,524,035

16 transactions · 11 stateful · 2026-05-19 02:37:11 UTC

Parallelism

88/100

Blocked

18%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,524,035  ·  16 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

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x67ddfac1…e4de

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x3db87ba8…85d1

0x065c9d…c394

2 touches
0 conflicts

0x65f28866…5913

0x065c9d…c394

2 touches
0 conflicts

0x870ce395…57d2

0x065c9d…c394

2 touches
0 conflicts

0x892daf6e…48d8

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x99a2130578…57dffc

← previous block·next block →recent activity