← previous blocknext block →recent activity

Analyzing

Block #75,682,144

14 transactions · 10 stateful · 2026-05-19 20:12:16 UTC

Parallelism

79/100

Blocked

20%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,682,144  ·  14 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

0x6eff5416…605d

0xea1b8e…c5ec

6 touches
3 conflicts

0x3dbd9177…e936

0xea1b8e…c5ec

4 touches
1 conflict

0xa8abcc19…3d83

0xea1b8e…c5ec

4 touches
1 conflict

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

2 touches
0 conflicts

0xa01afcf7…23d9

0x065c9d…c394

2 touches
0 conflicts

0xe7032a64…f384

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: 0xea1b8e4a…8fc5ec

3 conflicts on slot 0x6eff5416ed…f5605d

← previous block·next block →recent activity