← previous blocknext block →recent activity

Analyzing

Block #75,502,049

12 transactions · 10 stateful · 2026-05-19 00:06:33 UTC

Parallelism

83/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,502,049  ·  12 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

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0xb06e76e0…51cb

0x34b655…2a6f

4 touches
1 conflict

0xff140c5a…7bfe

0x34b655…2a6f

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

3 touches
1 conflict

0x07d5dc87…f727

0x065c9d…c394

2 touches
0 conflicts

0x443a3e47…f4a4

0x065c9d…c394

2 touches
0 conflicts

0x892daf6e…48d8

0x065c9d…c394

2 touches
0 conflicts

0xbfb92235…a6db

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

1 conflict on slot 0x5086c64a56…bb28ba

← previous block·next block →recent activity