← previous blocknext block →recent activity

Analyzing

Block #74,638,532

10 transactions · 10 stateful · 2026-05-14 23:54:13 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,638,532  ·  10 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

0x3e5a63e7…b4df

0x065c9d…c394

4 touches
1 conflict

0x8758a729…847c

0x065c9d…c394

4 touches
1 conflict

0xdcac6f00…cbed

0x065c9d…c394

3 touches
1 conflict

0xc0e340c8…9380

0x065c9d…c394

3 touches
1 conflict

0x70da11c3…1378

0x065c9d…c394

2 touches
0 conflicts

0xf352611e…5990

0x065c9d…c394

2 touches
0 conflicts

0xfed579bc…edd0

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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 0x3e5a63e792…81b4df

← previous block·next block →recent activity