← previous blocknext block →recent activity

Analyzing

Block #75,516,171

12 transactions · 8 stateful · 2026-05-19 01:43:20 UTC

Parallelism

83/100

Blocked

25%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,516,171  ·  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

0x892daf6e…48d8

0x065c9d…c394

4 touches
1 conflict

0x5f77d607…2c84

0x065c9d…c394

4 touches
1 conflict

0x5905410d…d12e

0x065c9d…c394

3 touches
1 conflict

0xe98a3afd…8b18

0x065c9d…c394

3 touches
1 conflict

0x172c5dcd…e2f2

0x065c9d…c394

2 touches
0 conflicts

0x4873218c…4b65

0x065c9d…c394

2 touches
0 conflicts

0xc29272bf…11c6

0x065c9d…c394

2 touches
0 conflicts

0x06e40499…165e

0x1d1325…2305

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: 0x065c9d28…a9c394

1 conflict on slot 0x892daf6e5d…6d48d8

← previous block·next block →recent activity