← previous blocknext block →recent activity

Analyzing

Block #74,771,537

23 transactions · 18 stateful · 2026-05-15 14:42:22 UTC

Parallelism

87/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,771,537  ·  23 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

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x03373974…9130

0x065c9d…c394

5 touches
3 conflicts

0xc850f1cc…8cc0

0x065c9d…c394

5 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

4 touches
1 conflict

0x0a2250a8…3cb1

0x34b655…2a6f

4 touches
1 conflict

0x0b28bf77…e53a

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xba38536db1…342b7d

← previous block·next block →recent activity